Related
Hi,
Just wanted to share my experience getting JPC Rom installed and rooted.
Prior to upgrade, I had the JP3 Rom, rooted with clockwork and 1-click lag fix.
I had some major issues installing JPC. In fact, I ended up with the dreaded USB logo a few times.
This is not a complete guide, but hopefully it will help avoid the problems I had.
1) Before installing the new rom, I strongly suggest that you Factory Reset the phone.
2) Install the JPC Rom using the other guides on this page. I used Odin and choose Repartition to get a clean install.
3) Here is where the problems started. After the rom installed cleanly and the phone rebooted, it would get stuck on the second Samsung logo and eventually go black. This happened to me twice. The fix I found out, is to go into Rececovery mode (Vol Up, Home, Power) after the install and clear the cache, reformat SD and factory reset. After you do this the phone will boot normally.
4) After that I followed the rooting guide on this forum, but ended up with the dreaded USB logo. If this happens to you, just go back into DOwnload mode and reflash with Odin again (following the guide in this forum)
IMPORTANT: I have TWO galaxy s phones. The strange thing is, one of them is VERY easy to get into Download or recovery mode. The other is almost impossible. For those of you that have a similar model to me that seems like it does not have a 3 button download or recovery mode you probably do.
I thought I was bricked, and tried for over an hour to get my second phone into download mode (take out battery, hold three buttons, put in battery, over and over again). I was about to give up, but found I was able to get the phone into download mode if I ....
1) Take Battery Out. Put it back in.
2) Plug phone into USB on computer (do not turn it on)
3) Now try to do the 3 button Download mode. Press all three buttons at one time and release power about 1 second after seeing Samsung logo.
Again my second phone I can very easily get to download mode 100% of the time. I am really not sure why the two phones would be any different. I hope this helps people that have a stubborn phone like mine.
P.S. I did not install Clockwork on JPC, but I did root the phone and installed 1 click lag fix. Phone is running VERY stable and all features seem to work (including Mobile AP).
I hope this helps others like me who tried to install update.zip as explained in some posts & got the dreaded USB logo on boot & didn't know what to do because I am sharp but no programming & all that. I got mine to go ahead ONLY after I put in my SIM & External SD card. With both OUT, I get the USB logo 100% of the times.
I hope this helps.
Ive installed jpc a few time now and a factory reser after flashing did it for me every time
Tutorial/Walkthrough How to update your Droid R2D2 Phone using 2.2 if it fails to update to Gingerbread 2.3.3 Build 4.5.1_57_DR2-32
After spending a few days dealing with my phone automatically downloading and trying to install the updating and failing at 25%. I had to fix this since it will killing my battery.
With the instructions below this should restore your phone to the stock version of your Droid R2D2. This method will not delete anything on your phone. I would recommend backing up everything before you proceed just in case something does go wrong but I didn't have any issues. It will only restore all the original settings on your phone. This includes unrooting your phone and restoring all apk's and system files edited/removed from your device.
WARNING : This must be done using your PC. Do not attempt this using your cell phone
This information is provided without warranty. I cannot be held responsible if you brick or damage up your cell phone. I simply wrote a walkthrough/tutorial to help deal with an update issue on your Droid R2D2. I did not produce the procedure or the steps below. I just simply consolidated all the information from multiple sources to make it easier to understand and execute. You are welcome to share this information anywhere you want. If needed I will reformat the instructions so it's easier to understand.
1) First download and install the Motorola RSD Lite v5.5 (I attached the file at the bottom of this thread)
2) Download the Motorola 5.2.0 Driver with Motohelper and install from the link below
Motorola Drivers - http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
3) Download the SBF Droid R2D2 file VRZ_A957_2.4.5_1FF_01.
http://www.multiupload.com/8XGQBDG3GV
4) Once you download the VRZ_A957_2.4.5_1FF_01 file. Unzip the file into a folder. You will be using this file shortly
5) Launch RSD Lite. Once the application is launched click on the button with the 3 dots.
Navigate to the SBF file you just unzipped and once you find it click open.
You will see on the right side in the File properties window
Filename: VRZ_A957_2.4.5_1FF_01.sbf
Creation Date: 09/15/2010 03:16:26
File size: 455655933
RAM DL Version: N / A
Bootloader Version: N / A
Platform: 4G OMAP
HAB Type: Signed Production
This is a video to give you an idea how to use RSD Lite. I used this as a guide to make sure I was doing everything in the correct order.
http://www.youtube.com/watch?v=9udWx-KXwGY&feature=player_embedded#!
6) (This step isn't necessary, but you can do it.)
Back up anything on your SD card to your computer. Plug in your Droid2 to the computer via USB cable. Pull down the notification menu/blind, choose USB connection, and then choose USB Mass Storage Device. Now there should be a removable storage in your "My Computer." Go through your SD card and back up your important things. Probably the DCIM and download folder. You should also make sure that your phone is set up to "Back Up Data." Go to the system menu (the 4 squares icon/button in the lower left), choose Settings, then Privacy, then make sure the "Back up my data" and "Automatic restore" are checked.
7) Plug the USB cable into your cell phone and Power off your phone. Once your phone is powered off, Slide out your keyboard and hold the Up Arrow and press the power button. You will see a boot loader screen pop up and it will say Battery OK, Transfer mode USB. You will see the computer detect the USB device and install the new drivers onto Windows.
If the drivers in Windows Fail DO NOT PROCEED. Reinstall the Motorola drivers and try this again
8) Once you see the Transfer mode say USB. Go back to RSD Lite and click Start. You will see the progress bar Executing and slowing moving up to 100%. Your phone will eventually Power on.
Do not unplug or touch it until it hits 100% if you unplug the phone early you risk screwing up the system files on your phone.
You'll know when it is done when the Progress field in the table of RSD Lite says complete. This will take between 5-10 minutes to complete
9) Once it hits 100% you will see the status change and say Please manually power up this phone.(You phone should be already powered on if not you could power it on). Once this is completed you could either turn off your phone and power it back on or you could click Close in RSD lite. A pop up window will appear saying Application is currently busy. Do you wish to continue click Yes.
UPDATE 10/27/11
After your phone reboots and doesn't get past the boot animation
1) Turn off your phone
2) Hold down X on the keyboard
3) Turn on your phone while continuing to hold X( it will boot into the recovery mode after the Motorola logo disappears)
4) When you get the Android guy with a '!' in a triangle push the search button on the keyboard (the magnifying glass button, two keys to the left of the space bar)
5) Select both 'wipe cache' and 'wipe data' from the menu.
6) Select Reboot your phone
10) Once you unplug your phone you should see all the apks or applications which were removed originally off the device back on the device (I removed practically everything and everything was restored). If you have used z4root you will notice if you open the application it is no longer rooted.
I had a Blue triangle in my notification bar. To clear this you will need to reactivate your phone. Dial *228 and press send. Once you hear the options press 1 to activate your phone. Once this is completed you get a message saying your phone is activated and to wait up to 15 mins. You will also see the blue triangle disappear and will see the 3g reappear.
11) Once you are connected start downloading over the air the new gingerbread update to your phone. Once it is complete your phone will reboot and start installing the file and once it completed you should have the new gingerbread update on your phone
To Root your Droid R2D2 Please follow the directions below (Special Thanks to psouza4 for creating this program) http://www.psouza4.com/droid3/
NOTE: Do this at your own risk. I am not responsible for any damage caused.
1. First step is that you need to make sure if all Drivers are installed.
2. Once that is done, download and install
(Windows) http://www.mediafire.com/?g226n7as6cb1y6e
(Mac/Linux) http://www.mediafire.com/?2ugcdue4cw7dtc5
3. Now, go to Settings > Applications > Development on your Droid R2D2 and enable the USB debugging option.
4. Now connect your device to the computer and make sure you select the ” Charge Only ” mode.
5. Go the folder where you extracted the zip and run MotorolaOneClickRoot.exe (Windows) or run_to_root_your_droid3.sh (Mac/Linux).
6. Once it finished just click any button to exit the program and you will see superuser installed on your Phone.
Thats it. Hopefully this was easy to understand and works for everyone.
I cannot even root my phone. It will not go past the first rebooting stage. Any advice?
Are you currently on 2.3.3 or you still on 2.2?
Also make sure debugging mode is on and you have the correct motorola drivers installed.
Cant get VRZ file to work.
Hello,
I am trying to run threw this to reset my R2D2 Droid 2. When I try and download the VRZ_A957_2.4.5_1FF_01 file from the the link you provided all I get is a rar file that doesn't work on RSD Lite. Am i missing something on the download sight for the VRZ file?
---------- Post added at 08:41 PM ---------- Previous post was at 08:09 PM ----------
Hello again,
Sorry for my stupidity I forgot a rar file is a compressed file and I had to download win zip to decompress it. Don't deal with a lot of compressed files. Thank you for all this info will post if I got it to work.
all good. let me know if it works or if you get stuck
ok so i've been working at doing this for roughly an hour the damn drivers won't install on my computer...
Where you able to install Download Motorola 5.2.0 Driver with MotoHelper or are you getting stuck when your phone is connected to the pc?
Worked for me
Awesome, worked for me from my mac. I did get an error between phases 2 and 3 of the root process, but it worked anyway:
* Running exploit [part 2 of 3]...
*
* Rebooting the phone... when the reboot is complete, you may need to unlock the phone to continue.
*
error: protocol fault (no status)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* Running exploit [part 3 of 3]...
remount succeeded
Does this only work for the Motorola Droid R2D2 or will it work for the Motorola Droid 2 with the Gingerbread 2.3.3? Which I thought are the same phone except for the R2D2 add-on's.
ehrune - I am glad it worked for you. I will write a email to psouza and see what he says on it or ill look for an new update maybe it was a known issue which is now fixed
dfthompson - I own a droid R2D2 phone which is technically a Droid 2 with all the add-ins as you stated. I wrote the instructions because if you were like me and deleted all the bloat and junk off your phone (when you originally purchased it) you are unable to do the OTH gingerbread update because it will fail once you are doing the installation.
The file is for 2.2
thank you for posting this. my phone has been trying to update for weeks every night around midnight and failing, this is a huge help.
I must admit, after using it for a week, this update sucks big-time. Everything is much slower, button presses take a second or two to register, etc. Anyone else seeing this?
well said, guys these instructions are flawless. basic computer skills required
Ok so does this exe file get run from the computer or launch it from the phone?
Sent from my DROID2 using XDA App
Everything is done using the PC the only thing you need to do with the phone is plug it into the computer and to turn it on to go into the boot screen as instructed.
Ehrune - Yes i notice a few things running slower. i removed a ton of apk's and changed some settings and it works a lot better
boot loop
the flash was 100% successful, but now my phone is stuck in a boot loop. should I try reflashing?
edit: I ended up booting into recovery & doing a factory reset. I was able to boot & run the update from there. Good thing I backed up first..
still locked! afther full flash & no way to factory reset on my phone
i only need to factory reset ive try any times with
---------------------------------------------------
Power down the DROID 2 by holding the power button and then selecting Power Off
Hold the X key on the keyboard and turn the power back on, keep holding down the X key until you see a yellow triangle icon
Now close the slider and hold down the Volume Up button, then press the Camera button while still holding volume up
A menu will appear and one of the choices will be "wipe data/factory reset" -- use the direction pad on they keyboard to select this option
Scroll down using the direction pad to the "yes" option and select it with the d-pad select key
---------------------------------------------------
& with
---------------------------------------------------
a. Turn off your phone
b. Hold down X on the keyboard
c. Turn on your phone while continuing to hold X
d. When you get the Android guy with a '!' in a triangle push the search button on the keyboard (the magnifying glass button, two keys to the left of the space bar)
e. Select both 'wipe cache' and 'wipe data' from the menu.
f. Reboot your phone
---------------------------------------------------
the hard reset no work for my with any form (& the keys7Buttons are working properly)
i been full flashed Thanks to your tutorial
But still locked
Too many attempts
any ideas¿?
I lost my SBF file for R2-D2, and the link not available for now (multiupload). can anyone help me where I can find the file?
Thanks
I'm also looking for the r2-d2 sbf. All the links I come across are 1 of 2 dead links. Either the multiupload or the adrive links. None of which are standing today. Am I to believe that no one has a copy to upload elsewhere? So can someone please point me in the right direction.
I already found the file.
u can email me for the link, I don't have any right to post the link here
my email: [email protected]
Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.
Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?
Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)
Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)
Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.
just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..
Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.
hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off
astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??
Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little
U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App
all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^
How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link
Looks like you are not having much luck. Did you try to factory reset?
astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much
A year or two so ago I updated my Motorola Milestone 2 to CyanogenMod, Android 4.1 I think, with no trouble.
I though that I'd take advantage of the CM11 (cm-11-20141003-UNOFFICIAL-milestone2.zip) and I attempted to upgrade to this.
I found that, after booting to the recovery utility, that would not accept this zip file. I noticed that czechop says:
Install my CM10.2 version >= 07.11.2013 first
So I installed cm-10.2-20140312-UNOFFICIAL-milestone2.zip and that went like a breeze. The phone booted up with the new version of Android. I then booted this into the recovery utility and found a new style of this ('Teamworks', I think) with a graphical interface. I found that this liked the cm11 zip file and it installed it without any apparent problem - it reported success and gave me two options - 'clear cache dalvik' (or something very similar), and 'reboot'. I opted for the clear cache, and that seemed to go OK, then I opted for 'reboot'.
This is where my heart sank, because the phone started to boot with the Motorola 'M' logo, then that faded out, then back in, then out. I see no little coloured LED light, and the phone seems to cycle around with the 'M' display, never getting anywhere.
What should I do now? I tried to boot the phone into the original Motorola recovery, holding down the keyboard 'X' key whilst switching on, but that just brings up a little picture of an orange triangle with a '!' in it.
Regards,
David
Hi,
Your best option is to ask for help in the thread you downloaded the rom from.
Good luck!
Thanks
Darth said:
Hi,
Your best option is to ask for help in the thread you downloaded the rom from.
Good luck!
Click to expand...
Click to collapse
Thanks. Unfortunately the site won't let me post there. I'm a new member.
Ah, There's no Q&A section. Normally now if you post in a development thread it automatically creates or posts in a thread in your device section Q&A.... But this won't work cause your section has no Q&A.
I will have your thread moved to your devices General section.
Good luck!
More on 'bricked' Milestone 2
datatone said:
A year or two so ago I updated my Motorola Milestone 2 to CyanogenMod, Android 4.1 I think, with no trouble.
I though that I'd take advantage of the CM11 (cm-11-20141003-UNOFFICIAL-milestone2.zip) and I attempted to upgrade to this.
I found that, after booting to the recovery utility, that would not accept this zip file. I noticed that czechop says:
Install my CM10.2 version >= 07.11.2013 first
So I installed cm-10.2-20140312-UNOFFICIAL-milestone2.zip and that went like a breeze. The phone booted up with the new version of Android. I then booted this into the recovery utility and found a new style of this ('Teamworks', I think) with a graphical interface. I found that this liked the cm11 zip file and it installed it without any apparent problem - it reported success and gave me two options - 'clear cache dalvik' (or something very similar), and 'reboot'. I opted for the clear cache, and that seemed to go OK, then I opted for 'reboot'.
This is where my heart sank, because the phone started to boot with the Motorola 'M' logo, then that faded out, then back in, then out. I see no little coloured LED light, and the phone seems to cycle around with the 'M' display, never getting anywhere.
What should I do now? I tried to boot the phone into the original Motorola recovery, holding down the keyboard 'X' key whilst switching on, but that just brings up a little picture of an orange triangle with a '!' in it.
Regards,
David
Click to expand...
Click to collapse
I am going to journal my experiences with this, in the hope that it will be useful to someone else.
Possibly the mistake that I made when flashing the CM11 (see above) is that I didn't put the md5 sum file onto the SD card with the archive. Note that all downloads have a .zip and a .zip.md5sum file. The phone output a message to say that it couldn't find a checksum, but that it was going ahead anyway. Possibly, had I put the md5sum file in, a fault with the zip file would have been detected and I may have been saved from this issue.
I have found references to a 'Motorola factory cable' which is a cable that is wired to persuade the phone not to worry about battery state and to operate the flashing utility from the usb cable power. this is obviously useful in the factory for programming the phone without a battery. See this link for information:
[unfortunately the site didn't allow me to attach a url to 'www dot droidforums dot net' where you might find a posting 'how-why-to-make-your-own-motorola-factory-cable', which is a well-writen and informative article]
My phone is in a state that the charger will operate to charge the battery as normal when the charger is plugged in with the phone off. It still shows the image of a battery filling up. Therefore I can keep my battery in good condition between recovery attempts, and I don't think I'll need any special cables.
My technique for putting the archives onto the SD card is to take the card out of the phone and put it into my laptop, so that I can simply manage the files on it with standard Windows file browser.
I can get to a very promising recovery utility by holding down the 'X' key on the keyboard whilst switching the phone on. The Motorola 'M' logo comes up and the screen then displays a 3D orange triangle with an exclamation mark and a little green Android man. If I press the keyboard '@' at this point, I jump into a recovery menu.
The recovery menu has options:
* 'reboot system now'
* 'apply sdcard:update.zip'
* 'wipe data/factory reset'
* 'wipe cache partition'
The 'apply sdcard:update.zip' seems to offer the promise of recovery.
I have tried placing both:
* cm-10.2-20140312-UNOFFICIAL-milestone2 (.zip and .zip.md5sum)
and
* cm-11-20141003-UNOFFICIAL-milestone2 (.zip and .zip.md5sum)
onto the sdcard (renamed as 'update.zip' and 'update.zip.md5sum').
In both cases the recovery utility says:
---
E:Can't open /cache/recovery/command
E:Can't open /cache/recovery/caller
-- Install from sdcard...
Finding update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
---
If I remove the update.zip.md5sum file, the result is identical. Therefore I don't think that this utility is using the md5sum for archive file verification. The problem that I seem to have at the moment is that I need an archive in the right format for the factory recovery utility.
I will be researching this and will add to this thread when I find an answer.
As a little bit of extra information, whilst fiddling about with the buttons during power up, I did manage to get a screen that said:
---
Bootloader
70.12
Battery OK
OK to Program
Connect USB
Data Cable
---
I guess that this is a lower stage in the bootloader chain, and suggests that there is hope if your phone is screwed up to the extent that you can't get the factory recovery utility. Thankfully, I don't seem to need to investigate what is required at the PC end to make use of this low level programming aid. (If anyone knows, it would be good to hear the details, for future reference and help to others).
Alas, I'm not sure what I did to bring this screen up - I fiddled with the volume, camera, and power buttons whilst the phone was starting up.
Regards,
David
Hello.
1. You don't need no 'factory cable'. All you need to come back to stock ROM is PC, RSDlite software, generic USB<->micro USB cable, and a stock ROM sbf file. The question what to do with a bricked phone was answered here plenty of times. Almost always the best way to bring a dead phone back to life is to flash a stock ROM (with bootloader version >= of version of current one).
2. You seem to have an older bootloader (the latest is 70.13 included in Ginger Bread ROMs), but you don't have to flash a newer one. Just remember, that bootloader is locked and cannot bet downgraded, so if you flash a newer one, you will never be able to flash generic ROMs with an older version. For example after I flashed 70.13 GB, a was unable to flash Froyo ROM over it (but you'll still be able to flash Froyo based CM7 with some tricks).
3. If you can access TeamWinRecovery (the graphicac one), you can simply clear system/cache partitions, and flash any custom ROM zip (for example Czechop's 10.2).
4. The stock recovery (with an exclamation mark, then you press both vol up and down to access menu) doesn't allow to flash unsigned zip images (and none of custom ROMs is signed with Motorola key). What you can do there is try to clear cache/data (factory reset). Sometimes some information in /data is preventing ROM from booting, if you changed ROM.
5. What You described is called a 'bootloop' - rebooting endlessly.
Progress
rabinhood said:
Hello.
1. You don't need no 'factory cable'. All you need to come back to stock ROM is PC, RSDlite software, generic USB<->micro USB cable, and a stock ROM sbf file. The question what to do with a bricked phone was answered here plenty of times. Almost always the best way to bring a dead phone back to life is to flash a stock ROM (with bootloader version >= of version of current one).
2. You seem to have an older bootloader (the latest is 70.13 included in Ginger Bread ROMs), but you don't have to flash a newer one. Just remember, that bootloader is locked and cannot bet downgraded, so if you flash a newer one, you will never be able to flash generic ROMs with an older version. For example after I flashed 70.13 GB, a was unable to flash Froyo ROM over it (but you'll still be able to flash Froyo based CM7 with some tricks).
3. If you can access TeamWinRecovery (the graphicac one), you can simply clear system/cache partitions, and flash any custom ROM zip (for example Czechop's 10.2).
4. The stock recovery (with an exclamation mark, then you press both vol up and down to access menu) doesn't allow to flash unsigned zip images (and none of custom ROMs is signed with Motorola key). What you can do there is try to clear cache/data (factory reset). Sometimes some information in /data is preventing ROM from booting, if you changed ROM.
5. What You described is called a 'bootloop' - rebooting endlessly.
Click to expand...
Click to collapse
Thank you very much. I have spent all day researching this.
I have discovered 'RSD Lite' and the ability to get the phone into the bootloader mode that I described by starting the phone and keeping the camera and volume buttons pressed.
I can boot to the stock recovery mode by powering up with the 'X' key pressed and then pressing '@'
I don't think that I can access TeamWinRecovery. There may be some way to do this that I don't know.
I did do a complete 'Nandroid?' backup of the system before I started this, so I guess that if I can get TeamWinRecovery or clockworkmod recovery back, I can restore to my previous working state.
What I have tried is 'G.O.T.’s OpenRecovery' to get a recovery installed. I put the OpenRecovery folder and the update.zip onto the SDcard and tried to flash it with the stock recovery utility. I got the "E:EOCD marker occurs after start of EOCD E:signature verification failed" error. I read that this means that I am not properly rooted (I thought I was) and I need to install 'vulnerable recovery' using an sbf file and RSD Lite. I have tried 'vulnerable_recovery_only_RAMDLD90_78.sbf' but the process errors, and what I read suggests that this might be due to the older bootloader version.
I tried to find an old stock android sbf for the phone, but all the links to such things seem to be dead.
I did try the factory reset from the stock recovery as a means to fix the bootloop. It didn't work.
You clearly know a lot about this. I would appreciate help to get back to something that works, maybe the last backup that I did.
I am also puzzled by why the upgrade to the CM11 from the CM10.2 failed. Did I do something wrong, or is there some compatibility issue with my phone? I never had a problem updating from the original motorola software to the cyanogenmod, then to the CM10.2.
I think I became a little over-confident.
Thank you in anticipation,
David
---------- Post added at 06:20 PM ---------- Previous post was at 05:59 PM ----------
rabinhood said:
Hello.
4. The stock recovery (with an exclamation mark, then you press both vol up and down to access menu) doesn't allow to flash unsigned zip images (and none of custom ROMs is signed with Motorola key).
Click to expand...
Click to collapse
Ah! the penny drops. The stock recovery that I can access will only install archives signed by Motorola. Hence the signature errors that I get when I try anything else. So I understand that if I can only get to the stock recovery, I can only use it to reinstall a stock android.
So the problem is where to find a stock sbf file to reinstall Motorola android as a first step to getting back to CM.
I guess that this is the only way to get back to clockworkmod recovery or teamwin recovery?
If I can get one of these recoverys running, I can simply restore to the last working system, I guess?
Regards,
David
---------- Post added at 07:07 PM ---------- Previous post was at 06:20 PM ----------
david.datatone said:
My phone is in a state that the charger will operate to charge the battery as normal when the charger is plugged in with the phone off. It still shows the image of a battery filling up. Therefore I can keep my battery in good condition between recovery attempts, and I don't think I'll need any special cables.
Click to expand...
Click to collapse
I realise that I was mistaken about this. There is no image of a battery filling up. The white LED by the USB socket lights when the charger is plugged in, but I can't be sure that the battery is charging.
Are you sure you're trying to flash a proper recovery? I remember there was a 'vulnerable recovery' for milestone 1, but no such thing for MS2. As you wrote, signature errors while trying to flash zips from stock recovery are due to lack of Motorola signature, not to problems with root. Root access has nothing to do with recovery, it is something much later/higher in system.
So again, what to do to unbrick the MS2:
1. Get a stock ROM - I suggest lates European one with 70.13 bootloader. There are also later Latin America ROMs, but they lead to more problems with custom ROMs. SBF's were published somewhere in these forums. If you cannot find them, write, and I'll upload one to some file sharing servers if I have time (I'll be staying at work for next 30 hours or so).
2. Get RSD lite and latest Motorola USB drivers (they're on the web), install. Before flashing remember you cannot use an USB 3 port - the best way is to turn USB 3 support off in computer BIOS.
3. Enter the flash mode in MS2. Connect is with generic USB cable to PC.
4. Run RSD lite, flash SBF, wait until phone reboots - it can take several minutes. If it freezes - try to enter stock recovery and wipe data/cache.
After these steps you should have a clear installation of stock ROM. Then you have to root, install Droid2 Bootstrap, install CM 10 or 10.1 -> 10.2 -> 11. If you have problems with these, write, and I'll write more detailed instructions.
PS. By the way, to enter TWR or CWM recovery you have to press vol down while a blue led is lit for a short time during reboot.
1000 Thanks
rabinhood said:
Are you sure you're trying to flash a proper recovery? I remember there was a 'vulnerable recovery' for milestone 1, but no such thing for MS2. As you wrote, signature errors while trying to flash zips from stock recovery are due to lack of Motorola signature, not to problems with root. Root access has nothing to do with recovery, it is something much later/higher in system.
So again, what to do to unbrick the MS2:
1. Get a stock ROM - I suggest lates European one with 70.13 bootloader. There are also later Latin America ROMs, but they lead to more problems with custom ROMs. SBF's were published somewhere in these forums. If you cannot find them, write, and I'll upload one to some file sharing servers if I have time (I'll be staying at work for next 30 hours or so).
2. Get RSD lite and latest Motorola USB drivers (they're on the web), install. Before flashing remember you cannot use an USB 3 port - the best way is to turn USB 3 support off in computer BIOS.
3. Enter the flash mode in MS2. Connect is with generic USB cable to PC.
4. Run RSD lite, flash SBF, wait until phone reboots - it can take several minutes. If it freezes - try to enter stock recovery and wipe data/cache.
After these steps you should have a clear installation of stock ROM. Then you have to root, install Droid2 Bootstrap, install CM 10 or 10.1 -> 10.2 -> 11. If you have problems with these, write, and I'll write more detailed instructions.
PS. By the way, to enter TWR or CWM recovery you have to press vol down while a blue led is lit for a short time during reboot.
Click to expand...
Click to collapse
I can't thank you enough. I'm currently downloading your stock ROM. I already have what I think is the latest verion of RSD Lite (6.1.6) installed on my Windows 8.1 laptop (I've read about problems with more contemporary versions of Windows, but I have successfully connected to the phone before now, just haven't had joy with flashing the file that I tried). I am fingers crossed that all will go well, and I'll certainly note that here. Otherwise I very much appreciate your offer of further help.
Bets regards,
David
david.datatone said:
I can't thank you enough. I'm currently downloading your stock ROM. I already have what I think is the latest verion of RSD Lite (6.1.6) installed on my Windows 8.1 laptop (I've read about problems with more contemporary versions of Windows, but I have successfully connected to the phone before now, just haven't had joy with flashing the file that I tried). I am fingers crossed that all will go well, and I'll certainly note that here. Otherwise I very much appreciate your offer of further help.
Bets regards,
David
Click to expand...
Click to collapse
recommend you return the original rom using RSDlite and start doing it all over again putting the rom CM10 and then cm11
Happy, happy, happy! Since I got it to work, thought I'd share.
~ caveat emptor, not responsible if this doesn't work for you ~
First off, I followed this very helpful post from DeeXii:
https://forum.xda-developers.com/note-4-tmobile/general/recovery-n910t-t3-marshmallow-pe3-guide-t3406870
I had flashed the N910TUVS2EPK2 stock from Odin after screwing up my phone doing other crap. In any case, after doing that, I obviously wanted root again! Note that this wasn't immediate - I flashed to this a couple months ago, so have been fully setup with gmail, and other account settings. So, the above link gave the best overall, simple step-through, with handy download links. It worked, and even better didn't lose any of my settings. (but, no guarantees, make sure you've backed up!)
Additional details that would be helpful:
- make sure you run Odin as Administrator.
- Odin: click the button next to AP, and then go select the twrp archive you downloaded
- Power off phone, hold boot into download mode (power, home, volume down at same time). click volume up when it says so.
- connect to Odin. you need to see the square just below ID:COM turn blue.
- Click Start to flash the twrp.
- IMPORTANT: after it flashes, the phone will auto-restart. *Quickly* pull out battery before it boots, otherwise it will put back stock recovery on you. (this happened to me - I had waited until it had fully booted, then powered down, then brought it up in recovery mode, and it wasn't twrp! - so remember, pull out battery right after it cycles after flashing)
- Put battery back in, and then boot into recovery by holding power-home-volume up simultaneously. If you end up seeing the nice pretty twrp squares, then this worked. It is interesting that there is also a message here stating that the kernel may very well write back the custom recovery. So, can't say if this will be permanent or not, but at least you can now flash the supersu. (subsequent reboot into recovery still seems to have twrp, so groovy!)
- (presuming you had already put the supersu on the sd card or internal memory - I used the systemless supersu), click install, select it and flash.
- just for kicks (not sure if this was needed or not), after flashing I saw an option to wipe cache/dalchik, so I did that too.
- rebooted (it took awhile, had to 'optimize' all the apps, etc.) - and I'm rooted!
If anyone has been trouble with specifically the N910TUVS2EPK2 build, then I hope this helps.
Thanks man, had the same issue. I figured it might be something to do with booting int OS. Sure enough with 6.0.1 EPK2 rom you MUST load into boot recovery right after flashing TWRP as you stated.
Something went wrong with my OTA update of EPK2 and it started to bootloop( 2 vibrates upon restart and then random amount of bootloops, and then random, soon-coming freeze upon loading in OS and continuing boot-looping) sometime after the update. I erased most of the old stuff via TWRP reinstalled EPK2 bootloader separately and then flashed EPK2 rom and it seems to be OK so far (knock on wood). We'll see hopefully it's not hardware issues like many people were reporting with bootlooping.
Can't you just uncheck the Odin option to reboot instead of the frantic battery pull?
Just wondering, as I'm going to do this later- thanks!
Steven.RN
Followup: Yep. Slip over to the options tab in Odin and uncheck "auto reboot". After Odin flashes TWRP, (the bar is all the way across the download screen, and the Odin Log says "succcess") go ahead, disconnect the phone from USB. Do your battery pull, replace battery. Close up the phone, then hit Volume up, home, and power at the same time- Bang! TWRP screen.
Further note: first time I did this flash, it didn't work, it just stopped in it's tracks. Then I realized I had to enable "developer mode" by clicking on the build number in the "About phone" sections in settings 5 times, going into Developer mode (the new option will present itself in the menu on settings), then: enable OEM unlock and USB debugging. Odin will flash TWRP just fine after that. (Duh on me!)
planetjeff said:
Happy, happy, happy! Since I got it to work, thought I'd share.
~ caveat emptor, not responsible if this doesn't work for you ~
First off, I followed this very helpful post from DeeXii:
https://forum.xda-developers.com/note-4-tmobile/general/recovery-n910t-t3-marshmallow-pe3-guide-t3406870
I had flashed the N910TUVS2EPK2 stock from Odin after screwing up my phone doing other crap. In any case, after doing that, I obviously wanted root again! Note that this wasn't immediate - I flashed to this a couple months ago, so have been fully setup with gmail, and other account settings. So, the above link gave the best overall, simple step-through, with handy download links. It worked, and even better didn't lose any of my settings. (but, no guarantees, make sure you've backed up!)
Additional details that would be helpful:
- make sure you run Odin as Administrator.
- Odin: click the button next to AP, and then go select the twrp archive you downloaded
- Power off phone, hold boot into download mode (power, home, volume down at same time). click volume up when it says so.
- connect to Odin. you need to see the square just below ID:COM turn blue.
- Click Start to flash the twrp.
- IMPORTANT: after it flashes, the phone will auto-restart. *Quickly* pull out battery before it boots, otherwise it will put back stock recovery on you. (this happened to me - I had waited until it had fully booted, then powered down, then brought it up in recovery mode, and it wasn't twrp! - so remember, pull out battery right after it cycles after flashing)
- Put battery back in, and then boot into recovery by holding power-home-volume up simultaneously. If you end up seeing the nice pretty twrp squares, then this worked. It is interesting that there is also a message here stating that the kernel may very well write back the custom recovery. So, can't say if this will be permanent or not, but at least you can now flash the supersu. (subsequent reboot into recovery still seems to have twrp, so groovy!)
- (presuming you had already put the supersu on the sd card or internal memory - I used the systemless supersu), click install, select it and flash.
- just for kicks (not sure if this was needed or not), after flashing I saw an option to wipe cache/dalchik, so I did that too.
- rebooted (it took awhile, had to 'optimize' all the apps, etc.) - and I'm rooted!
If anyone has been trouble with specifically the N910TUVS2EPK2 build, then I hope this helps.
Click to expand...
Click to collapse
thanks for the info, might give it a shot tonight. you have a link to the software update so i can load it with odin?
Thanks for the post. Where can I find the stock N910TUVS2EPK2 ROM?
Charlie Rock said:
Thanks for the post. Where can I find the stock N910TUVS2EPK2 ROM?
Click to expand...
Click to collapse
sammobile.com
Sent from my SM-N910T using Tapatalk