Okey, before FRG83D I rooted my phone with SuperOneClick. Then I decided to go back to the original ROM, and update to FRG83D. As you know, this revoked my root access. So now I unlocked the bootloader and ran Superboot. However I don`t get rooted. My suspicions are that because my old Superuser apk is left, something goes wrong. Plz help me figure this out!
Well all need a root for 2.2.1
Sent from my Nexus One using XDA App
Shivammcool said:
Well all need a root for 2.2.1
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Are you telling me there is NO way to root 2.2.1 ? :O
No, I think the other guy is just thinking of a root-without-unlock method.
You are already unlocked. So it's just a matter of changing the system correctly to root it. Easiest way is to probably flash an already rooted stock build over it. (I assume you want to remain stock)
Or at least you need to find the correct way to root 2.2.1, which is hard because there are probably a lot of people out there looking for a root without unlocking, so that will pollute your search results.
Edit: Of course, I could be way off base and not know what I'm talking about.
Yup, flash a rooted stock rom, like Geo's.
I still don't know why people love to make things harder on themselves than it needs to be lol.
Okey, this is kinda crazy, because Adblock is working and has all permission, but nothing else!
Sent from my Nexus One using XDA App
MrSvedberg said:
Okey, this is kinda crazy, because Adblock is working and has all permission, but nothing else!
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Not familiar with Adblock, but if it is similar to AdFree it just works by replacing your /system/etc/hosts file with one that directs every advertising address to the loopback address, thus preventing the apps from loading. If that file was in place before you lost root, it will continue to block ads for you.
Okey, but if I just want to flash CM, what do I do? Can't get to recovery :/
Sent from my Nexus One using XDA App
You're unlocked, right? Super easy :-D
Download a recovery *.img (or extract it from a recovery .zip).
Reboot your N1 to fastboot mode (press and hold VOL-DOWN while powering on - press Power to select Fastboot USB when the option is presented).
Connect your USB cable.
Run fastboot flash recovery recovery.img (replacing "recovery.img" with the appropriate file name). When complete, you have an aftermarket recovery again.
Boot to recovery and install whatever ROM you want
codesplice said:
You're unlocked, right? Super easy :-D
Download a recovery *.img (or extract it from a recovery .zip).
Reboot your N1 to fastboot mode (press and hold VOL-DOWN while powering on - press Power to select Fastboot USB when the option is presented).
Connect your USB cable.
Run fastboot flash recovery recovery.img (replacing "recovery.img" with the appropriate file name). When complete, you have an aftermarket recovery again.
Boot to recovery and install whatever ROM you want
Click to expand...
Click to collapse
Thx a lot m8, but could you dumb that down just a little bit? Still a bit n00b in the area x)
Sent from my Nexus One using XDA App
Those steps are broken down a bit more specifically (including prerequisites) in this thread, which I found from the NexusOne Wiki, which is a great place to look for such common information.
Done it, and I'm 110 % sure I did it right! Still does not work!
Sent from my Nexus One using XDA App
What part are you having trouble with?
Can't boot into recovery...
Sent from my Nexus One using XDA App
MrSvedberg said:
Can't boot into recovery...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I'm afraid you'll have to be more descriptive than that.
HOW are you trying to boot to recovery? There are several methods:
1) Issue the adb reboot recovery command
2) Boot to the bootloader (press and hold Volume-Down while powering on), use the volume keys to scroll down to Recovery, and the power button to launch it.
3) Use an application like Quick Boot to reboot directly to recovery from the OS, though that may require a working root.
Have you tried these methods? If so, what happened? What did you see on the screen?
Number 2. Just seeing an Android and a triangle.
Sent from my Nexus One using XDA App
MrSvedberg said:
Number 2. Just seeing an Android and a triangle.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Then that is the stock recovery. Flashing a third-party recovery was not successful. Did you receive any error messages from the fastboot flash recovery recovery.img command?
Your bootloader IS unlocked, right? You have a padlock icon on the bottom of the screen immediately after poweron?
The flash was successful, no error messages. And yes, the padlock is there.
Sent from my Nexus One using XDA App
MrSvedberg said:
The flash was successful, no error messages. And yes, the padlock is there.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
What recovery image are you trying to use?
Related
So I have a bit of an issue. Over the weekend my power button stopped working like it has for many people.
I finally got to a computer last night and was able to turn it on using a method I had read about.
I was using madaco's desire port but I didn't have the option for wake with trackball baked into it. Which I need to have my phone usable. So I had another ROM baked on his site with that option in it but I forgot to tick the option to have the .zip signed. (I'm using an older recovery, had been to lazy to update)
I didn't realized it wasn't signed until I had go into recovery, wiped everything and then attempted to flash at which time it said no because it wasn't signed. So I said F it I'll do it in the morning.
So today I realized I can't boot the phone up because I had wiped everything, including the ext partition. It just sits at the X screen with the unlocked paddle lock on it. Due to this I can't access it with ADB to get to recovery.
If I restart the phone and put it into HBOOT I can't select recovery because you have to press the power button to select the option.
I also tried finding a fastboot command to boot into recovery but didn't locate one.
SOO
Does anyone have a clue how I can get this damn thing into recovery? I'm normally really good with this stuff but I am stumped at this point.
And before anyone says it I can't exchange it because my screen is cracked.
If you can grab a kernel and and recovery image on your PC you can boot them using
fastboot boot <kernel image> <recovery image>
Is that going to get me to a point where I can flash a new rom on it? I was running all of my cache on SD so when I wiped it is messed the rom up.
It already has Amon_RA recovery on it, the release prior to the newest one. So do I really need to flash another one to it?
All I can think of is possibly reverting to stock via the passimg method, but I can't remember if you need to use the power button to confirm during the process?
Once you have a working ROM, you can root via superoneclick, and install superboot to boot into recovery.
Problem is, you'll then have a stock recovery...
Once you're booted and rooted though, you can always use adb, or ROM Manager right?
Sent from my Nexus One using XDA App
danger-rat said:
All I can think of is possibly reverting to stock via the passimg method, but I can't remember if you need to use the power button to confirm during the process?
Once you have a working ROM, you can root via superoneclick, and install superboot to boot into recovery.
Problem is, you'll then have a stock recovery...
Once you're booted and rooted though, you can always use adb, or ROM Manager right?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yeah that's the route I'm thinking about taking. But I think there are option you have to use the power button to confirm.
I'm messing around with different boot.img right now to try and get it to boot. If I could just get the damn thing to boot I'd be all set cause I can use adb from that point. But right now when it stops at the X screen ADB can detected the phone but if you try to access the shell you get "failed to link /system/bin/sh
Thanks for the input man
If your bootloader is unlocked, you can re-image with fastboot.
Also, if you're not unlocked, I'm pretty sure the passimg only selects options with the volume keys...
Sent from my Nexus One using XDA App
I went with the superboot method. When I ran the .bat files it restarted the device and put it into recovery. I flashed a fresh ROM from there.
It's made it to the boot animation so I'll see if it fully boots up in a minute .
Okay, I'm back in action. Thanks for the in put guys.
Great!
D'ya need an unlocked bootloader to use superboot (I've never used it)?
Sent from my Nexus One using XDA App
Just discovered this gem:
http://forum.xda-developers.com/showthread.php?t=825909
Sent from my Nexus One using XDA App
danger-rat said:
Great!
D'ya need an unlocked bootloader to use superboot (I've never used it)?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I'm pretty sure you do. It says you'll probably need to as a foot note in the directions for superboot.
I may be wrong, I haven't kept up on much relating to rooting the Nexus since it first came out.
I think you're probably right... Thanks!
Sent from my Nexus One using XDA App
running rod's miui rom and was trying to remove excess crap via titanium pro. when trying to remove facebook it would reboot and give an error message about signature failure. so i thought i'd see if it would successfully remove a different app. rod included a fancy widget app that i had no desire for. when trying to remove that, it did a number on my n1. i cannot get into the recovery mode or anything.
this is a video of what the phone now does. no matter if i pull the battery or what.
http://www.youtube.com/watch?v=6a4DP3IjZiQ
That's an interesting one.
When you turn it on - this is the first thing you see? No "X" at all?
Did you try ADB to see if it sees the device?
Looks just like radio flash, but with radio flash there are no recovery messages, if I remember correctly.
no, i get the un-animated X, and then it goes straight to this. regardless if i hold down the trackball or not.
what do i need to do to try to adb to it? i don't fool with adb ever, just when i first rooted/unlocked it.
Put a diff update.zip for another rom on your sdcard. Lemme know if it works
Sent from my Bionixed SGH-T959 using XDA App
brnbock said:
Put a diff update.zip for another rom on your sdcard. Lemme know if it works
Sent from my Bionixed SGH-T959 using XDA App
Click to expand...
Click to collapse
i took enoms rom, renamed it update.zip and placed it on the sdcard. still nothing, same thing.
if i press the powerbutton whilst on the android out of the box thing it says.
"ClockworkMod Recovery v2.5.1.0
Finding Update Package........
Opening Update Package.......
Verifying Update Package......
Installing Update....."
this is shown in the video, but blurry and hard to read.
well, if im doing things right..... adb remount said it successfully did so.
(edit) ok, i can definitely connect via adb, i just ran the reboot bootloader command and the phone rebooted..... albeit back to that stupid looping screen.
any other ideas folks...... i'm up against a wall here.
i am able to get this in terminal
[email protected]:~/Android/tools$ ./adb devices
List of devices attached
HT02KP901120 recovery
[email protected]:~/Android/tools$
You need a rom that can be flashed as an update.zip, most are not flashed that easy. Can you get into fastboot?
Sent from my Bionixed SGH-T959 using XDA App
brnbock said:
You need a rom that can be flashed as an update.zip, most are not flashed that easy. Can you get into fastboot?
Sent from my Bionixed SGH-T959 using XDA App
Click to expand...
Click to collapse
i don't think so
Try booting into fastboot, if you can your good if not then I will do some digging.
Sent from my Bionixed SGH-T959 using XDA App
brnbock said:
Try booting into fastboot, if you can your good if not then I will do some digging.
Sent from my Bionixed SGH-T959 using XDA App
Click to expand...
Click to collapse
well, i cant get to the recovery screen to initiate fastboot. if i use adb reboot-recovery it just reboots the phone and goes back to the looping crap i'm stuck at.
if i try any fastboot commands, i get nothing. i just can't get it to do anything other than respond to adb commands.
a fella from nexus one forums suggests that perhaps my bootloader is messed up and needs to be restored? that sound possible?
That was this fella, and I'm actually more convinced that the recovery is stuck trying to do an update... xD
Sent from my Nexus One using XDA App
danger-rat said:
That was this fella, and I'm actually more convinced that the recovery is stuck trying to do an update... xD
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
haha. the omnipresent danger-rat is indeed the fella.
I was hoping Jack or Rusty would be here to check my logic...
Here's what we believe so far:
1 - phone appears to be in recovery, and trying to install an update.
2 - phone is in recovery, so adb is (kinda) working.
3 - there's no update.zip on the SD card.
4 - trying to overwrite the recovery via adb gives a "device or resource busy" response...
My guess is that if the install process can be killed, then you should be able to re-gain control?
...I've no idea how to kill processes via adb... :-(
Sent from my Nexus One using XDA App
Woooooo HOOOOOOOO!!!!!!!!!!!!!!!!!!
i'm not entirely sure what i did......... but i think i have it. i transfered amon's 1.7.0 img to the sdcard and aptly renamed it recovery.img. after just now trying to restart to see if i could get fastboot to do anything it must have found the recovery.img and reflash amon. i'm looking at amons recovery now as i type.
i just rebooted and now i'm back into rods miui...... phone is working fine.
danger-rat said:
I was hoping Jack or Rusty would be here to check my logic...
Here's what we believe so far:
1 - phone appears to be in recovery, and trying to install an update.
2 - phone is in recovery, so adb is (kinda) working.
3 - there's no update.zip on the SD card.
4 - trying to overwrite the recovery via adb gives a "device or resource busy" response...
My guess is that if the install process can be killed, then you should be able to re-gain control?
...I've no idea how to kill processes via adb... :-(
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
just wanted to say thanks so much for all your effort and help man.
now a new quick question... which is what started this whole fiasco.
how can i remove unwanted apps from rods miui rom?
noremacyug said:
now a new quick question... which is what started this whole fiasco.
how can i remove unwanted apps from rods miui rom?
Click to expand...
Click to collapse
adb shell
su
rm -rf /system/app/nameofapp.apk
once the apps are deleted:
(on the phone)
go to settings--> manage applications
and delete any leftover files pertaining to the programs you just deleted
Reboot
Then reboot and make a backup
*EDIT*
You may need to reboot after removing the programs for those file to show up in Manage Applicaions
Just as a posted on another thread, now my phone is running android1.1, after i turned the screen off, i can no longer wake it up by pressing any button or sliding keyboard, but the keyboard light can be lighted...
What do you mean by "turned the screen off" turned the phone like completely off or just put it to sleep? If you flashed, then check to see if your radio/spl matches up to the roms requirements. If not, then thats the reason. If you just put it to sleep, try factory resetting your phone via holding power+home to get into recovery, then alt+w
Sent from my SGH-T959V using XDA Premium App
Light-라이트 said:
What do you mean by "turned the screen off" turned the phone like completely off or just put it to sleep? If you flashed, then check to see if your radio/spl matches up to the roms requirements. If not, then thats the reason. If you just put it to sleep, try factory resetting your phone via holding power+home to get into recovery, then alt+w
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Thanks very much for your reply... i mean put it to sleep, i have factory resetting my phone many times, but it doesn't work ...
Now i flashed the RC29.nbh, root the phone and flash an Android 1.5 rom, the phone can be turned on and can answers incoming calls, but the screen cannot display,i wonder if there is something wrong with the LCD? thanks.
sparkpang said:
Thanks very much for your reply... i mean put it to sleep, i have factory resetting my phone many times, but it doesn't work ...
Now i flashed the RC29.nbh, root the phone and flash an Android 1.5 rom, the phone can be turned on and can answers incoming calls, but the screen cannot display,i wonder if there is something wrong with the LCD? thanks.
Click to expand...
Click to collapse
It could be the rom youre using. Try updating to the latest radio/spl and downloading frosense or any of the cm7 roms. I dont think its the lcd. If it turns on at all, then the lcd's not the problem. Thats what im thinking because i dropped my phone in water before, the lcd was damaged. SCreen wouldnt even turn on, but i could hear everything. So yea. .
Sent from my SGH-T959V using XDA Premium App
Light-라이트 said:
What do you mean by "turned the screen off" turned the phone like completely off or just put it to sleep? If you flashed, then check to see if your radio/spl matches up to the roms requirements. If not, then thats the reason. If you just put it to sleep, try factory resetting your phone via holding power+home to get into recovery, then alt+w
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Light-라이트 said:
It could be the rom youre using. Try updating to the latest radio/spl and downloading frosense or any of the cm7 roms. I dont think its the lcd. If it turns on at all, then the lcd's not the problem. Thats what im thinking because i dropped my phone in water before, the lcd was damaged. SCreen wouldnt even turn on, but i could hear everything. So yea. .
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Well, the problem is updating recovery, i have tried many times, but after i flashed the recovery using fastboot or flash_image, the recovery mode cannot be displayed normally, only the last line" Build: 1.7.XX" can be seen, there's no items above. So i've no idea how to flash roms. Can i flash roms in the fastboot mode?
Are you rooted? If you are, then i have a solution for you.
Assuming you have root- Download ROM manager from the android market (the free version) and open it. It'll ask for superuser permissions. Click allow. then click flash clockworkmod recovery. Then itll give you a list of htc dream or magic. Click the dream and let it download. After it finishes, itll say "clockworkmod download complete" or something like that. Then theres another option on the app that says "reboot into recovery" click that, and flash the recovery you want. I recommend that you just use cwm recovery as i am using it on my g1. .
If you dont have root, then.... I have no idea. Sorry. And no you cant flash via fastboot.
Sent from my SGH-T959V using XDA Premium App
Light-라이트 said:
Are you rooted? If you are, then i have a solution for you.
Assuming you have root- Download ROM manager from the android market (the free version) and open it. It'll ask for superuser permissions. Click allow. then click flash clockworkmod recovery. Then itll give you a list of htc dream or magic. Click the dream and let it download. After it finishes, itll say "clockworkmod download complete" or something like that. Then theres another option on the app that says "reboot into recovery" click that, and flash the recovery you want. I recommend that you just use cwm recovery as i am using it on my g1. .
If you dont have root, then.... I have no idea. Sorry. And no you cant flash via fastboot.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
my phone is rooted, but the Rom manager have to be force closed once i run it, i have tried different versions of Rom manager and different roms.
I have flashed clockworkmod recovery 2.5.0.7 via fastboot, but it didnt show anything when i enter recovery then.
Now I dont think i can flash Roms via recovery, so i prepare to do so via fastboot, i'm learning how to make *.zip packages for fastboot, its different from packages for recovery as i learned.
sparkpang said:
my phone is rooted, but the Rom manager have to be force closed once i run it, i have tried different versions of Rom manager and different roms.
I have flashed clockworkmod recovery 2.5.0.7 via fastboot, but it didnt show anything when i enter recovery then.
Now I dont think i can flash Roms via recovery, so i prepare to do so via fastboot, i'm learning how to make *.zip packages for fastboot, its different from packages for recovery as i learned.
Click to expand...
Click to collapse
easy fastboot is just that; an easy way to use fastboot for the novice. also try droid explorer, a very simple to use program that may help you download what you need. both are free and easy to find links to - just google search or search these forums.
Light-라이트 said:
Are you rooted? If you are, then i have a solution for you.
Assuming you have root- Download ROM manager from the android market (the free version) and open it. It'll ask for superuser permissions. Click allow. then click flash clockworkmod recovery. Then itll give you a list of htc dream or magic. Click the dream and let it download. After it finishes, itll say "clockworkmod download complete" or something like that. Then theres another option on the app that says "reboot into recovery" click that, and flash the recovery you want. I recommend that you just use cwm recovery as i am using it on my g1. .
If you dont have root, then.... I have no idea. Sorry. And no you cant flash via fastboot.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Now I find whats going on finaly, the problem is the LCD...
i have two Dreams early, a white one given by friends that i didnt know whether it's good, a black one that is working fine. Then i replace the LCD and the mother board between the two phones, then the white one works well, and the black one come up with such problem... So i just bought a LCD and prepare to repair it ...
Thanks a lot for your help..
Well I decided to call Google about the boot loader recovery not working as it should. I was hoping this call would help them to work on another update but they say that's the way its supposed to work. Here's the email Instructions:
1. Power down your device
2. Press and hold both volume keys and the power button to enter
Bootloader mode
3. Press the volume keys to cycle to the Recovery mode option
4. Press the power button to select Recovery mode
5. From the Recovery mode screen, press and hold the Power button then
press the Volume up button.
6. Use the volume buttons to select wipe data/factory reset.
7. Select Yes -- delete all user data.
8. The factory data reset process will now start. Once its finished,
select 'Reboot system now.'
The only option we have in the new recovery is to wipe data. Maybe for those having problems accessing twrp or cwm will be able to a access it with step 5. I don't know haven't rooted yet. So I decided to ask about nvflash and they said they're not going to release any nvflash tools or files.
um, yup. thats how stock bootloader and stock recovery work. lol
whats the issue? if your not even rooted, you wouldn't even know if you have an issue or not with the new bootloader.
Are you saying that you can't flash a different recovery? Or that when you do you still get the same stock recovery? I'm not quite sure what the issue is here, because that is exactly how the stock bootloader, and recovery are supposed to work.
Are you making sure to unlock fastboot before trying to flash recovery. I don't recall seeing or hearing anyone say anything about not being able to get to clockwork mod once its installed.
xjman said:
Are you saying that you can't flash a different recovery? Or that when you do you still get the same stock recovery? I'm not quite sure what the issue is here, because that is exactly how the stock bootloader, and recovery are supposed to work.
Are you making sure to unlock fastboot before trying to flash recovery. I don't recall seeing or hearing anyone say anything about not being able to get to clockwork mod once its installed.
Click to expand...
Click to collapse
No. I saw people posting they couldn't get go cwm and could only see the red exclamation point. And I was just saying maybe after choosing recovery then holding volume up and power it would then go to cWm or twrp. I was hoping for someone to try it who is still on 3.41 Recovery. A lot of people downgraded back to 3.39 or whatever version it was
kieso said:
I was hoping for someone to try it who is still on 3.41 Recovery. A lot of people downgraded back to 3.39 or whatever version it was
Click to expand...
Click to collapse
I can confirm that to get in to the stock recovery you hold down 'power' and then tap 'vol up'.
At present I am running the latest CWM touch recovery. This boots straight into it from the bootloader without any extra button presses.
My personal preference to go into CWM is from either QuickBoot or ROM Manager.
Sent from my Nexus 7 using xda app-developers app
smirkis said:
didn't know being informed makes me an asshole. stupid me, reading and understanding.
for what its worth, im on the newest bootloader, and selecting recovery goes straight to twrp. which is the recovery i installed.
Click to expand...
Click to collapse
I wonder why some on 3.41 can't go straight to twrp and some can. Sorry for the ahole comment I thought you were trying to be a smartass towards me. I'm just trying to find out as much info from people before I root. I am experienced at flashing and a little adb but I just read a lot of HELP BRICKED MY NEXUS posts. Did you use wugs toolkit or adb to unlock and root?
mr_tris said:
I can confirm that to get in to the stock recovery you hold down 'power' and then tap 'vol up'.
At present I am running the latest CWM touch recovery. This boots straight into it from the bootloader without any extra button presses.
My personal preference to go into CWM is from either QuickBoot or ROM Manager.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the info. I'm going to try unlocking and rooting when I get home. I really want to use the OTG cable and the 720p mod.
kieso said:
I wonder why some on 3.41 can't go straight to twrp and some can. Sorry for the ahole comment I thought you were trying to be a smartass towards me. I'm just trying to find out as much info from people before I root. I am experienced at flashing and a little adb but I just read a lot of HELP BRICKED MY NEXUS posts. Did you use wugs toolkit or adb to unlock and root?
Click to expand...
Click to collapse
When I first flashed TWRP onto my Nexus 7 after that official 4.1.2 OTA update, I wasn't able to boot into it. I then flashed it again via fastboot, and then booted the TWRP image that was on my computer, and then TWRP loaded.
I believe TWRP does work normally now as well (I can boot into it and reboot into it).
kieso said:
I'm going to try unlocking and rooting when I get home.
Click to expand...
Click to collapse
Well if I was you I'd just use mskips toolkit, its absolutely epic it'll save you a lot of farting around. I take it that your fully updated? ( Not that it matters) You seem to know and understand your way around adb so just go for it and enjoy.
Its works smooth as silk and save you a lot off time. The options available to you are just staggering!
http://forum.xda-developers.com/showthread.php?t=1809195
Sent from my Nexus 7 using xda app-developers app
Thread Cleaned
No need for personal insults, lets just try to help each other out and show each other some respect.
going to recovery from bootloader works fine after 3.41.....wat r u talkin abt? (i m stock rooted+twrp)
oh yea...u hav 2 remove that recovery stock.p file thingy first.
There are plenty of people that are having issues with recovery on 3.41 bootloader.... Its confirmed some have it some don't.
The issue is that with 3.41 bootloader on some Nexus 7 Devices a custom recovery is unbootable no matter how you try, every time it will try to load recovery and fail at a black screen then reboot into the OS. It does not matter how you try from ADB reboot to recovery or from bootloader with USB attached or not.
psycho2097 said:
going to recovery from bootloader works fine after 3.41.....wat r u talkin abt? (i m stock rooted+twrp)
oh yea...u hav 2 remove that recovery stock.p file thingy first.
Click to expand...
Click to collapse
Ohh crap I read about that in some thread. Any idea exactly what has to be done. The only way I can get into cwm is with ROM toolbox but I have to reflash cwm every time then hit boot into recovery.
kieso said:
Ohh crap I read about that in some thread. Any idea exactly what has to be done. The only way I can get into cwm is with ROM toolbox but I have to reflash cwm every time then hit boot into recovery.
Click to expand...
Click to collapse
In your system folder there's a file called 'recovery-from-boot.p'
Go into a file manager with w/r access and rename it ' recovery-from-boot.p.bak'
When the system boots it reads that file and resets the recovery to stock, by changing the name you remove the problem.
Sent from my Nexus 7 using xda app- app developers
mr_tris said:
In your system folder there's a file called 'recovery-from-boot.p'
Go into a file manager with w/r access and rename it ' recovery-from-boot.p.bak'
When the system boots it reads that file and resets the recovery to stock, by changing the name you remove the problem.
Sent from my Nexus 7 using xda app- app developers
Click to expand...
Click to collapse
Thank you for all the help! I appreciate it.
kieso said:
Thank you for all the help! I appreciate it.
Click to expand...
Click to collapse
No problem, a click on the 'Thanks' button for me and my colleagues on this thread would really make our day. :thumbup:
I hope you get sorted mate, I wouldn't be able to sleep at night until I got custom recovery working properly on any of my devices!
Sent from my Nexus 7 using xda app-developers app
i tried changing the name of the file, but.. after reboot, the tablet gets stuck on google screen, recovery never loads... any suggestion? Thanks =)
Hello, needing some help. Unlocked boot loader and tried to install twrp 2.5.0.0.m7. Phone Booted into recovery but was not able to install superuser as download directory would not show up. I can still fastboot flash to phone and can on a couple occasions get twrp to start.
at this point I just want the phone to work work. It is stuck at "htc quietly brilliant" screen. I could see the directory from androzip but when I try to install Superuser it wont find it.
lbcontractor said:
Hello, needing some help. Unlocked boot loader and tried to install twrp 2.5.0.0.m7. Phone Booted into recovery but was not able to install superuser as download directory would not show up. I can still fastboot flash to phone and can on a couple occasions get twrp to start.
at this point I just want the phone to work work. It is stuck at "htc quietly brilliant" screen. I could see the directory from androzip but when I try to install Superuser it wont find it.
Click to expand...
Click to collapse
Looks like you used the wrong version of twrp it should be 2.5.0.0m7wls
Sent from my Eliptic Nexus 7
bigdaddy619 said:
Looks like you used the wrong version of twrp it should be 2.5.0.0m7wls
Sent from my Eliptic Nexus 7
Click to expand...
Click to collapse
This one addresses the sd issue?
lbcontractor said:
This one addresses the sd issue?
Click to expand...
Click to collapse
u flashed the wrong recovery....that's the international version...
go here & download/flash the correct one...
http://forum.xda-developers.com/showpost.php?p=40336506&postcount=2
lbcontractor said:
This one addresses the sd issue?
Click to expand...
Click to collapse
I have dl and installed that version. It did find super user and installed. That being said it still gets stuck on that screen. I think perhaps I have deleted factory rom. I have been watching vid on installing Viper rom but it kinda brushes over moving the file to the phone. I assume it is a fastbook flash command? I get a unknown partition error and cannot determine image if i do that. Help has been great so far thanks all.
See if this post helps you
http://forum.xda-developers.com/showthread.php?t=2317989
Its not seeing device. Also getting unable to mount cache.
Sent from my GT-P5113 using xda app-developers app
Also what about usb otg? Might that work?
Sent from my GT-P5113 using xda app-developers app
lbcontractor said:
Its not seeing device. Also getting unable to mount cache.
Sent from my GT-P5113 using xda app-developers app
Click to expand...
Click to collapse
are you able to get into bootloaer in recovery?
Yes I can do almost anything but get the damn thing to work. Now the phone will go directly to twrp at start up. I can get usb otg to mount and start to load zip. But it hangs and reboots before it extracts. My thought is root hasnt taken do to wrong img file on front end. So my thought is to reinstall ruu and if I get it to go and try rooting afterwards. ??????
Sent from my GT-P5113 using xda app-developers app
Yea, relock bootloader and RUU.
Real easy tool to relock if your interested.
http://forum.xda-developers.com/showthread.php?t=2236814
I dont know what else to do at this point.
Sent from my GT-P5113 using xda app-developers app
Did you download the tool and relock the bootloader than RUU the phone?
You can try this also.. pretty easy
http://forum.xda-developers.com/showthread.php?t=2236418
budeone said:
Did you download the tool and relock the bootloader than RUU the phone?
You can try this also.. pretty easy
http://forum.xda-developers.com/showthread.php?t=2236418
Click to expand...
Click to collapse
I did and finally got my phone back. It was long and scary process but finally got it back to factory settings. Thank to all that helped.
Real cool.. Good luck.. have fun...