Related
My Droid X is special... It boots into bootloader automagically every time i turn it on. It says its ok to Program when the battery is charged so I have successfully linked it to RSD lite following the documented steps and have run it 4 or 5 times, getting the same result each time. It gets all the way through and then reboot the phone which immediately goes back into bootloader. RSD lite then errors out with a FAIL. The message says
'unable to switch phone to BP pass through mode' or something to that nature.
I have also run it on an ubuntu linux machine where it runs successfully but with no real results.
I have tried so many things, including trying to flash the newest froyo update.zip through the stock recovery. I've wiped multiple times, rebooted etc... running the update.zip gets all the way to updating radio image where it errors out.
assert failed: motorola.update_cdma_bp("/tmp/rdl.bin", /tmp/bp.img")
E:Error in /sdcard/update.zip
(status 7)
Installation aborted.
is it possible I have a hardware issue?
I have followed rootz wiki to a T with no results
Do I have a fix?
I've searched and searched and found no fixes for the errors i've encountered. Thanks for any help
Same thing happened to me when I tried to apply the SBF. I was trying to use a virtual machine and it just wouldn't work. I loaded a boot camp partition on my macbook pro, installed 32bit WinXP, booted into XP and it worked the very first time.
I've tried it on a 32bit xp machine, a 64bit win 7 machine, and an ubuntu machine. The 2 windows/RSD sbf installs gave me the same error... the Ubuntu runs everything, goes to reboot phone.. and the phone just reboots back to bootloader... am i missing a step?
i somehow managed to change the bootloader from 29.01 to 30.01 if that means anything.. man this is frustrating
this should fix all
http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html
Gman25 said:
http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html
Click to expand...
Click to collapse
Negative... followed this to a T. Really i need someone to address the errors i've described since they seem to be rare
trillonometry said:
Negative... followed this to a T. Really i need someone to address the errors i've described since they seem to be rare
Click to expand...
Click to collapse
Well, Like I said, I had the same exact error you are having. Perhaps try re-downloading the SBF file or get it from a different source.
If nothing else, take it back to VZW. Don't lie, but just tell them you were trying to restore your phone and this is what you got.
mrnosox said:
Well, Like I said, I had the same exact error you are having. Perhaps try re-downloading the SBF file or get it from a different source.
If nothing else, take it back to VZW. Don't lie, but just tell them you were trying to restore your phone and this is what you got.
Click to expand...
Click to collapse
Yeah that looks like my last resort. unfortunately I bought it as a brick off ebay thinking i could get it working since it was booting into bootloader so i dont know how much help verizon will be since i didnt purchase through them
trillonometry said:
Yeah that looks like my last resort. unfortunately I bought it as a brick off ebay thinking i could get it working since it was booting into bootloader so i dont know how much help verizon will be since i didnt purchase through them
Click to expand...
Click to collapse
Just covering all bases here, but are you *sure* you are using RSD Lite 4.7 and dragged the .ini patch into its program folder? A lot of people forget that last part.
And if it really is a brick, hope you didn't pay much for it =/.
I had a similar problem with the switching to BP bypass mode on a Win 7 64-bit system, I had done this before on the same system a couple of weeks ago successfully. I ended up switching to an old system I have with a fresh 32-bit XP install, everything went without a hitch the first time after accepting the firewall alerts that popped up around the time that the phone switched to the BP Bypass mode.
There may be firewall issues, I've seen a post on it, but can't for the life remember where.
Hope it helps.
i had the same problem. i got to the error message saying something about Loading RAM or something idk. i was trying to apply BigX's theme over an old one via ADB cuz im having mounting issues on CM.
but anyways. after the 4th time it finally went threw. im running Win 7 64-bit Ultimate. i was watching a movie at the sametime on my comp(2 screens) and i closed all my backgrounds besides those two and it worked. as soon i clicked start on the RSD, i went back to the movie and didnt mess with it at all. dont really know if doing any of dat helped but it worked for me. good luck with ur troubles. if u find a solution post it up just incase this happens to me again and i dont get it fixed this time lol
djtoonjr said:
i had the same problem. i got to the error message saying something about Loading RAM or something idk. i was trying to apply BigX's theme over an old one via ADB cuz im having mounting issues on CM.
but anyways. after the 4th time it finally went threw. im running Win 7 64-bit Ultimate. i was watching a movie at the sametime on my comp(2 screens) and i closed all my backgrounds besides those two and it worked. as soon i clicked start on the RSD, i went back to the movie and didnt mess with it at all. dont really know if doing any of dat helped but it worked for me. good luck with ur troubles. if u find a solution post it up just incase this happens to me again and i dont get it fixed this time lol
Click to expand...
Click to collapse
Yeah I am definitely going to redownload the sbf and try again in the morning too late to get into it now for me. IF i ever get it fixed then I will post what I did so here's hoping... I got the same set up too so I will throw on some iron man2 and tinker with a brick all day!
trillonometry said:
My Droid X is special... It boots into bootloader automagically every time i turn it on. It says its ok to Program when the battery is charged so I have successfully linked it to RSD lite following the documented steps and have run it 4 or 5 times, getting the same result each time. It gets all the way through and then reboot the phone which immediately goes back into bootloader. RSD lite then errors out with a FAIL. The message says
'unable to switch phone to BP pass through mode' or something to that nature.
I have also run it on an ubuntu linux machine where it runs successfully but with no real results.
I have tried so many things, including trying to flash the newest froyo update.zip through the stock recovery. I've wiped multiple times, rebooted etc... running the update.zip gets all the way to updating radio image where it errors out.
assert failed: motorola.update_cdma_bp("/tmp/rdl.bin", /tmp/bp.img")
E:Error in /sdcard/update.zip
(status 7)
Installation aborted.
is it possible I have a hardware issue?
I have followed rootz wiki to a T with no results
Do I have a fix?
I've searched and searched and found no fixes for the errors i've encountered. Thanks for any help
Click to expand...
Click to collapse
Device ID: 0
13:54:14, October 16, 2010
Line: 713
ERROR: Phone[0000]: The "Motorola_Flash" Interface could not be found.
The super-file is not secure and for re-flash;
the phone needs a super-file that is not secure and for reflash.
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\MIFlash.cpp
Device ID: 0
13:54:14, October 16, 2010
Line: 589
ERROR: Flash failure: Phone[0000]: Error switching phone to BP Pass through mode (Error Code: be),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=257
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
13:54:38, October 16, 2010
Line: 518
ERROR: AP Die ID: 20700014ed845d010000f8ff0100
13:54:39, October 16, 2010
Line: 525
ERROR: BP Die ID: 0000000000000000b55432890485
13:54:39, October 16, 2010
Line: 532
ERROR: AP Public ID: 30efc09241ed7c2c973d65140aecb2a2b2d655d8
13:54:39, October 16, 2010
Line: 539
ERROR: BP Public ID: 040000000500000002000000ffff00002d003289
14:02:04, October 16, 2010
Line: 1836
ERROR: Phone[0000]: Error switching phone to BP Pass through mode
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:02:14, October 16, 2010
Line: 713
ERROR: Phone[0000]: The "Motorola_Flash" Interface could not be found.
The super-file is not secure and for re-flash;
the phone needs a super-file that is not secure and for reflash.
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\MIFlash.cpp
Device ID: 0
14:02:14, October 16, 2010
Line: 589
ERROR: Flash failure: Phone[0000]: Error switching phone to BP Pass through mode (Error Code: be),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=257
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
ok- I am sure you all ready know all this but I just wanted to double check. You said that you followed the instructions on rootzwiki to the T? Well the only instructions I see on the rootzwiki are for the 2.1 sbf. So here is what I am wondering... are you using the 2.1 sbf or the 2.2 sbf? Bc the rootzwiki is a link to the 2.1 sbf not the 2.2 sbf. the name of the 2.2 sbf is...
VRZ_MB810_2.3.15_1FF_01
You said you bought the phone bricked. I was thinking that maybe it was one of those cases where the guy had 2.1, then got the 2.2 ota, decided he wanted to go back to 2.1, tried to sbf and bricked his phone. If that is the case then you need the newly leaked 2.2 sbf and not the one linked to from rootzwiki.
Like I said - I am sure you know all this- but just in case I thought I would ask if you are using the new 2.2 sbf.
just trying to help.
just to update everyone on the issue here. I am intelligent enough to have tried everything findable on the internet to try and solve my issue. I came to the conclusion that it was an internal hardware issue and the device was not fixable. It has since been put on eBay for parts.
I have replaced it with a working DX so all is well though!
thanks for everyones help
Would this work to SBF my phone iwith Linux??? COPIED and made file name change from Rootzwiki.
I would try it on my phone but I just SBF'ed using windows/RSD method . Got my phone where I like it ,for now...
Linux Instructions:
1.Download*sbf_flash*(credit [mbm])
2.Unzip the SBF*(Download Above)
3.Put your Droid X into bootloader (turn phone off and hold volume down and the camera button while pressing the power button)
4.Connect your USB
5.Open a terminal window.
6.Run "cd*Downloads"
7.Run*"chmod +x sbf_flash"
8.Run "sudo*./sbf_flash*VRZ_MB810_2.3.15_1FF_01.sbf"
9.Wait and finish!
Thank You
I know this is an old thread but I'm going to add my solution just in case it happens to someone else and they have to go on a google journey that yields nothing.
you need:
2.3.320 recovery only SBF
1.connect phone to RSD Lite 4.8
2.select 2.3.320 recovery only sbf
3. flash it
4. phone will now reboot hooray
5. turn off phone and boot into recovery
6. wipe data/factory reset and you should be good to go.
I was so scared that I had bricked my 800 dollar phone but shes back now (best buy purchase)
.... And I'll add mine just in case. (I know, several months later.)
I had the same issue with the "BP passthrough" error. Tried several SBF files multiple times with the same (failed) results. I did a fresh installation of drivers and RSD Lite on another machine, and voila! It worked!
Hope this helps someone!
Andy
I had a lot of problems trying to root my phone after I upgraded my firmware to 2.2 using the SuperOneClick application however, I did manage to come up with a fix that worked for me.
(Please note: that I can not be held responsible for any damage this may cause to your phone)
When I first tried using the SuperOneClick I notice that the applicaiton would hang "waiting for device". I received the following advice but it didn't work:
When the application gets to the "Waiting for device" prompt complete the following.
-Unplug usb from phone
-Uncheck usb debugging
-Replug usb cable
-Unplug usb cable
-Recheck usb debugging
-Replug usb cable.
Rince and repeat until successful rooting.
If you have tried this and it didn't work then try the following:
Google JuneFabrics PdaNet Andriod and download / install the PdaNet for Android.
During the installation you will be prompted to install new USB drivers so that your phone can connect to your PC. However, if you have ever connected your phone to Kies or for file transfer then say no to the install.
Once you have the program installed go back to SuperOneClick and run as administrator.
Happy Rooting...
It worked for me on my second try without having to download PdaNet, but I know it can be a pain in the a$$
SuperOneClick worked for me on first try on Captivate 2.2!
Also worked first try on my friend's Bell Galaxy S.
z4 not workin on this?
SteveCheeseman said:
z4 not workin on this?
Click to expand...
Click to collapse
Haven't read any posting of it working.
I couldn't get z4root to work
Sent from my SAMSUNG-SGH-I896 using Tapatalk
No z4root is not working. The exploit it use only works on 2.1 not 2.2. The app will FC / freeze or just close.
Also just a note on the SOC. Please don't start thread saying the usb unplug/replug method worked or didn't for you. This IS the way it works. If it worked on your first try, well good for you go buy a lottery ticket cause it's your lucky day.
The success rate is 100% but the number of tries is random. Could work on your 5th attemp like it can on your 1st or 2th.
Sorry guys for my silly question
but what is super one click and where can i get it ?
Thanks
Or you could just download my new Rogers 2.2 ROM Fire Fly and not have to worry since it comes rooted
adamholden85 said:
Or you could just download my new Rogers 2.2 ROM Fire Fly and not have to worry since it comes rooted
Click to expand...
Click to collapse
Firefly's awesome - you're everywhere adam!
Clockworks Recovery
Hi,
I recently rooted my phone with Superoneclick, but I can't get the Clockword recovery working.
I got the following error message.
E:fialed to verify whole-file signature
E:signature verification failed
Could someone help me out on this?
Thanks,
I got error in sdcard\update.zip
(error 7) when trying to install on rogers captivate on eclaire 2.1
why??
tried 2 diff root files.
shaddowman said:
Sorry guys for my silly question
but what is super one click and where can i get it ?
Thanks
Click to expand...
Click to collapse
If you go to google and search Super One Click download, you should be able to find it that way.
help
Cokeaddict said:
Hi,
I recently rooted my phone with Superoneclick, but I can't get the Clockword recovery working.
I got the following error message.
E:fialed to verify whole-file signature
E:signature verification failed
Could someone help me out on this?
Thanks,
Click to expand...
Click to collapse
i have the same thing happening to me. tried superoneclick several times, it works, i flash clockworkrecovery works, then i reboot and get the same message. -brent
Cokeaddict said:
Hi,
I recently rooted my phone with Superoneclick, but I can't get the Clockword recovery working.
I got the following error message.
E:fialed to verify whole-file signature
E:signature verification failed
Could someone help me out on this?
Thanks,
Click to expand...
Click to collapse
Normal 3e clockwork recovery has signature verification which prevents a lot of the files here from being flashed on your phone (because they are not officially verified/signed). There's a modified 3e clockwork file that you can put on your phone. When I first installed it for my own rooted phone, I used untermensch's 3e_recovery_installer.zip which was easy and didn't require any terminal stuff.
hook up your phone to a computer with the galaxy s drivers (using PDAnet works great). then run the script. the script is kinda wonky so it took a few tries to work.
let us know how that goes
adamholden85 said:
Or you could just download my new Rogers 2.2 ROM Fire Fly and not have to worry since it comes rooted
Click to expand...
Click to collapse
I found that to actually flash this ROM, you need to do the steps I mentioned, above.
with 2.2 jp3 or jp2 , u don't need do root it so far . use Odin3 downgrade it to 2.1 and use oneclickroot .......... ( use adb to enter download mode with some model can't use 3 button . "fastboot reboot download"
this superoneclick does not work
I have tried this method multiple times, all seems to go right, i get superuser showing up in my app drawer, yet when i use clockworks recovery to flash a new recovery I get the "failed to verify whole-file signature" followed by the next line "signature verification failed Installation aborted"...
I have the rogers captivate, it has been updated to android 2.2, Android system recovery <3e>.
I have also tried the adb version of rooting with the same result. Not sure if anyone has actually gotten theirs to work on rogers, they really should make a video or a more detailed list. Im not new to rooting or anything, but the instructions versus the results are not adding up. Hope there are others with success stories that they would like to share.
WOW you know you have 3e recovery. Search info on it.
you will find that 3e has signature verification... thats why your zips fail!!!
you will also find the 3e recovery FIX..
IT WAS FULLY EXPLAINED 2 POSTS ABOVE YOURS this friggin page!!! up 10 inches!!!
WHAT THE F????
http://forum.xda-developers.com/showthread.php?t=909213
Fail
I have tried the untermensch's 3e_recovery_installer.zip method, but ended up bricking my phone. Thankfully rogers sent me a new one when i complained that it was the devices fault. Has this worked on anyones captivate.
yeah the version you flashed was for a vibrant not a captivate...
use the instructions Posted above and in my sig "3e fix"
why is this the most difficult thing this month when its an old problem?
I just bought me a Dell Streak and I want to root it & install a different ROM, I'm fairly new with rooting, I rooted my HD2 so I'm not totally new.
Android Version 2.2
Baseband GAUSB1A134031-US
KERNEL 2.6.32.9-perf
Build 14844
I haven't seen a guide with the build 14844, so can I still root mine using a different build version guide? and can I install the 2.2.2 ROM?
Can someone point me in the right direction.
Hey i used superoneclick v1.7 rageinthecage lol its rage somthin haha anyway it was super easy and go to dells site and get the correct drivers also there are tons of threads here to guide u in the right direction hope this helps
I see that you are new to xda just remember search, search, search its the key NOT NEW JUST NOT MANY POSTS LOL!
Thanks for that link Fleur, as I'm having the same trouble as well.
Now, I'm not new to rooting, and installing custom ROMs and all that. I've had an HD2, Vibrant, G2, Captivate, and now a Dell Streak. It's just a pain to root right now lol.
Well I downloaded SOC, installed Dell Streak Mini 5 drivers from Dell's website, and tried to root, but I get this message in the end:
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
error: closed
FAILED
I tried the other exploit option as well, but no luck. Help would be appreciated man
saintsmmx said:
Thanks for that link Fleur, as I'm having the same trouble as well.
Now, I'm not new to rooting, and installing custom ROMs and all that. I've had an HD2, Vibrant, G2, Captivate, and now a Dell Streak. It's just a pain to root right now lol.
Well I downloaded SOC, installed Dell Streak Mini 5 drivers from Dell's website, and tried to root, but I get this message in the end:
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
error: closed
FAILED
I tried the other exploit option as well, but no luck. Help would be appreciated man
Click to expand...
Click to collapse
i didnt have the right drivers when mine did that but i did use rage and i followed the guide to a t that was on here if that dont work try v1.5.1 ive seen ppl have success that way hope that helps man
Oh yea check debugging on 2!
Assuming you have the correct drivers installed, An easy way to root a stock Streak is as follows.
1. Verify that you already have debug enabled, then turn off Streak completely.
2. Make sure the USB cable is connected to PC and Streak.
3. Power on Streak normally.
4. Start SuperoneClick 1.7 as soon as you power on the Streak. Do not wait for it to finish booting, Select rageagainstthecage and press root. ( I always run as admin but not sure if its really needed )
5. The Root program will wait until it detects the Streak and do its thing.
6. You should see Superuser being installed.
7 Streak is now Rooted.
The end. Works for me on Stock 318 every time.
kable said:
assuming you have the correct drivers installed, an easy way to root a stock streak is as follows.
1. Verify that you already have debug enabled, then turn off streak completely.
2. Make sure the usb cable is connected to pc and streak.
3. Power on streak normally.
4. Start superoneclick 1.7 as soon as you power on the streak. Do not wait for it to finish booting, select rageagainstthecage and press root.
5. The root program will wait until it detects the streak and do its thing.
6. You should see superuser being installed.
7 streak is now rooted.
The end. Works for me on stock 318 every time.
Click to expand...
Click to collapse
thats what i did
fleurdelisxliv said:
thats what i did
Click to expand...
Click to collapse
i did it with it fully booted up. just plugged it in with USB debugging turned on (dont mount the card) and away it went
kable said:
Assuming you have the correct drivers installed, An easy way to root a stock Streak is as follows.
1. Verify that you already have debug enabled, then turn off Streak completely.
2. Make sure the USB cable is connected to PC and Streak.
3. Power on Streak normally.
4. Start SuperoneClick 1.7 as soon as you power on the Streak. Do not wait for it to finish booting, Select rageagainstthecage and press root. ( I always run as admin but not sure if its really needed )
5. The Root program will wait until it detects the Streak and do its thing.
6. You should see Superuser being installed.
7 Streak is now Rooted.
The end. Works for me on Stock 318 every time.
Click to expand...
Click to collapse
it worked thanks
Hey all,
I'm trying to downgrade to 1.2.6 via RSD Lite and I am getting this error at 93%
22:38:29, July 21, 2011
Line: 958
ERROR: Phone[0000]: Multi Interface threads timedout and did not complete the flashing operation
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\MIFlash.cpp
Device ID: 0
22:40:29, July 21, 2011
Line: 2008
ERROR: Phone[0000]: Error switching phone to BP Pass through mode
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
22:40:39, July 21, 2011
Line: 767
ERROR: Phone[0000]: The "Motorola_Flash" Interface could not be found.
The super-file is not secure and for re-flash;
the phone needs a super-file that is not secure and for reflash.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\MIFlash.cpp
Device ID: 0
22:40:39, July 21, 2011
Line: 1194
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
22:40:39, July 21, 2011
Line: 610
ERROR: Flash failure: Phone[0000]: Multi Interface threads timedout and did not complete the flashing operation (Error Code: 8c),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=No Codegroup
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
22:50:50, July 21, 2011
Line: 1506
ERROR: Error getting subscriber unit information.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Click to expand...
Click to collapse
It seems to try to 'Switch phone to BP Pass through mode' at 93%... fails to do so, and times out. Anyone else had this happen?
I can still start the phone, get into the OS, it says 1.2.6...so I thought maybe it did work...however, when i then try to update after rooting, the update fails to install. Thoughts?!?! Thanks!
Crymson said:
Hey all,
I'm trying to downgrade to 1.2.6 via RSD Lite and I am getting this error at 93%
It seems to try to 'Switch phone to BP Pass through mode' at 93%... fails to do so, and times out. Anyone else had this happen?
I can still start the phone, get into the OS, it says 1.2.6...so I thought maybe it did work...however, when i then try to update after rooting, the update fails to install. Thoughts?!?! Thanks!
Click to expand...
Click to collapse
try flashing to .83 maybe where you unlocked bl or on a different ota?
I got my phone with 1.8.3 on it and was trying to downgrade to 1.2.6. The downgrade failed, however, the phone does start, and it does say 1.2.6 and I can root...I just can't perform system update, as the install fails.
You are saying I should root, and then go to 1.8.3 via RSD Lite, and not through the system update?
Also, I have not unlocked the bootloader yet, is that needed for this? I thought it was only needed for CWM?
If the ota updates aren't working I would use rsd. You do not need an unlocked bootloader I was asking if u have one cause it could have affected the phone
Sent from my MB860 using XDA Premium App
If i root in 1.2.6, then use rsd to update to 1.8.3, wont superuser be gone, and won't I lose root?
Will the afterupdate.bat in gladroot still work if i use rsd to update and not ota?
When I get home, I'm going to try to flash 1.2.6 again, using some of the tips and tricks for flashing SBFs. Shorten the name, put it in C:, run RSD as admin, and update to v5.3.1 (was using v5)
Hopefully this will stop the RSD error
Try rebooting your computer, and reinstall drivers from Motorola.
If that fails use another computer.
Sent from my MB860 using Tapatalk
Try the new rad and update drivers
Sent from my MB860 using XDA Premium App
Yes! Thanks to everyone for their help! I updated RSD Lite, and switched computers, and it flashed perfectly now. I have since unlocked the bootloader, went to 1.83, and got root. Now to pick what rom i want, any suggestions?
Crymson said:
Yes! Thanks to everyone for their help! I updated RSD Lite, and switched computers, and it flashed perfectly now. I have since unlocked the bootloader, went to 1.83, and got root. Now to pick what rom i want, any suggestions?
Click to expand...
Click to collapse
I suggest deleting RSD. Now that you have the unlocked bootloader using it will brick your phone. I unlocked mine and have not tried any gingerbread roms yet. I am still running 183 with ginger blur. Everything works great on it, and I want to let the new roms develop for a while and work out the kinks before I jump in. Just an option.
plasticglock said:
I suggest deleting RSD. Now that you have the unlocked bootloader using it will brick your phone. I unlocked mine and have not tried any gingerbread roms yet. I am still running 183 with ginger blur. Everything works great on it, and I want to let the new roms develop for a while and work out the kinks before I jump in. Just an option.
Click to expand...
Click to collapse
No. I've unlocked my bootloader and I've successfully flashed the 1.8.3 SBF multiple times with no issues.
If you flash the HKTW Gingerbread or 4.5.91 through fastboot, you won't have to worry about bricking your device.
I think I bricked my KF, can anyone help?
I rooted it fine, I belive.
I installed the GoogleServicesFramework.apk to /system/ and to /system/app/, both by accident. I know that it only should be in /system/app/. After I rooted I used Root Explorer to delete the GoogleServices.apk from /system/. I had problems, restarted my KF and I'm now stuck at the splash screen in constant bootloop.
What can I do?
I did screw my KF, post back up.
bal1985 said:
I did screw my KF, post back up.
Click to expand...
Click to collapse
Did you try press and hold on the power button for 20 seconds then power on?
Sent from my SPH-D710 using xda premium
fishfuzz said:
Did you try press and hold on the power button for 20 seconds then power on?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Yes, it goes right back to splash screen. When I first turn my KF on, I hear my PC make a sound like the USB is connected which it is, then my screen flickers and my PC makes a sound again, like it's being disconnected. I just get the bootlop splash screen. My KF has been on for quite a bit now. I have no clue what to do with ADB or what not.
Like I said, I tried following the Unbricking guide here at XDA but not sure what I'm doing.
I tried typing this:
C:\Users\Brett>cd c:\KindleFireRoot\files
c:\KindleFireRoot\files>adb shell
$ cd data/local
cd data/local
$ cd tmp
cd tmp
$ ls
ls
output
busybox
zergRush
$ ./zergRush //run zergRush
./zergRush //run zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x000151e0
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40119cd4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd195bb 0xafd39357
[*] Popping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
c:\KindleFireRoot\files>
Click to expand...
Click to collapse
It says restarting as root? My KF never restarted or anything. It's still in bootloop. I don't know what I'm doing or what I just did?
I had a similar issue, I had to fix /system/app permissions with adb and everything worked fine after that. I don't recall the exact process but if you read through the stickied thread in this forum you'll find it.
neilrl79 said:
I had a similar issue, I had to fix /system/app permissions with adb and everything worked fine after that. I don't recall the exact process but if you read through the stickied thread in this forum you'll find it.
Click to expand...
Click to collapse
I checked the thread, its too confusing. Anyways, my PC is not recognizing my Kindle all of a sudden. Any clue whats going on? ADB worked fine last night.
I just called Amazon, there sending me a replacement. By the time I get an answer here I could just have a new one.
bal1985 said:
I just called Amazon, there sending me a replacement. By the time I get an answer here I could just have a new one.
Click to expand...
Click to collapse
Did you tell Amazon you rooted it?
bal1985 said:
I checked the thread, its too confusing. Anyways, my PC is not recognizing my Kindle all of a sudden. Any clue whats going on? ADB worked fine last night.
Click to expand...
Click to collapse
Hi, I am going to root and change my rom which is something only experienced people should do. I messed it up and now don't want to be bothered reading how to fix it and learn to prevent it from happening again.
I will now hassle the manufacturer to fix my incompetence which I will just go on ahead and recreate most likely within days.
Thelgow said:
Hi, I am going to root and change my rom which is something only experienced people should do. I messed it up and now don't want to be bothered reading how to fix it and learn to prevent it from happening again.
I will now hassle the manufacturer to fix my incompetence which I will just go on ahead and recreate most likely within days.
Click to expand...
Click to collapse
I have experience with rooting phones. I don't have to experience with rooting tablets. And before I rooted I got advice from some a**hole on here stating that it was simple with little problems. If I knew before hand that I was going to go through all this and deal with people like you, I would have stayed away. The last thing I want to deal with on my weekend off is dealing with "internet bad-asses" who have a giant "internet ego" and think they are better then everyone else because they can root a Kindle? Come on man, go get laid or something, I don't care if you can root better than me. This isn't a pissing contest, it's a help forum, for people that actually want to learn and want the help. Seriously, how much time do you have on your hands to post comments like you do? Do you just patrol the fourms looking for potential victims? Your like the forum pedophile/nazi.
So if anyone truly wants to help please let me know. I don't want to send my KF back and risk having them find out I rooted it, can't afford one as this one was a gift. But my KF is in pretty bad shape so I might luck out.
Anyways if you can help me get out of this mess I'd appreciate it.
This is where I'm at now: http://forum.xda-developers.com/showthread.php?t=1356257&page=35
asb2164 said:
Did you tell Amazon you rooted it?
Click to expand...
Click to collapse
Yeah, thats the first thing I told them!
I just mentioned to them that I just got my KF, I was using it today, it shut off and when I powered it on it just bootlooped.
The Amazon CSR asked me a few questions. Did you power it off, etc. I told her I tried several USB cords, and chargers. I also said that I left my KF off over night, tried everything. She put me on hold, came back and said my KF was defective and it's happened quite a bit to other customers. She said my warranty is good for a year and there sending a new one out now.
All I can do is try man, I never said that they wont find out. But right now I have an expensive paperweight on my hands. I'd be very surprise if Amazon even checks if its rooted, highly unlikely.