Hello all, I have a friend with a G1 that is currently running Cyanogen 4.0.4. He is interested in updating to the latest stable release, but has had trouble booting after he does. Since I have no experience with the G1 or Android in general, I was hoping someone might be able to walk us through the process.
I know his phone is rooted, but I'm not sure what he used to do so. I also think he could probably use a radio update.
Thanks for your time!
xiton said:
Hello all, I have a friend with a G1 that is currently running Cyanogen 4.0.4. He is interested in updating to the latest stable release, but has had trouble booting after he does. Since I have no experience with the G1 or Android in general, I was hoping someone might be able to walk us through the process.
I know his phone is rooted, but I'm not sure what he used to do so. I also think he could probably use a radio update.
Thanks for your time!
Click to expand...
Click to collapse
This link provides all the steps needed to upgrade from 4.0.4 to the current release
http://wiki.cyanogenmod.com/index.p...version_less_than_4.1.99_or_other_rooted_ROMs
Download the Android 1.6 Recovery Image (it has "-ota-" in the filename):
http://www.4shared.com/file/164243978/15081498/signed-dream_devphone_userdebu.html
Download the latest CyanogenMod ROM for your device:
http://n0rp.chemlab.org/android/upda...7.1-signed.zip
1) Hold power and turn the phone off
2) Start up in recovery mode by holding home and pressing power.
3) You are now in recovery mode.
4) Press Alt-W to wipe all data
5) Press Alt-A to apply any zip from sd
6) Choose signed-dream_devphone_userdebug-ota-14721.zip (You won't see the entire filename)
7) When it is done it will ask you to reboot to complete the installation. Press Home+Back
8) You will be returned to the recovery screen in a few minutes, be patient.
9) Press Alt-A to apply any zip from sd
10) Choose update-cm-4.2.7.1-signed.zip
11) After the update is complete, hold Home and press Back to restart. (May take up to 15 minutes to boot)
12) Complete the setup process
i have looked everywhere (i think) for signed-dream_devphone_userdebug-ota-14721.zip Where did it go... i'm also on 4.0.4 and want all the googly goodness if you have- or- can find a link?? thanks so much. i've learned alot from u guys, sorry for not posting
Found a mirror using the Google (real complicated stuff, not recommended for beginners)
http://pomac.netswarm.net/mirror.html/mirror/android/adp1/android-1.6
It has both
signed-dream_devphone_userdebug-img-14721.zip
&
signed-dream_devphone_userdebug-ota-14721.zip
yozpalang said:
Download the Android 1.6 Recovery Image (it has "-ota-" in the filename):
http://www.4shared.com/file/164243978/15081498/signed-dream_devphone_userdebu.html
Download the latest CyanogenMod ROM for your device:
http://n0rp.chemlab.org/android/upda...7.1-signed.zip
1) Hold power and turn the phone off
2) Start up in recovery mode by holding home and pressing power.
3) You are now in recovery mode.
4) Press Alt-W to wipe all data
5) Press Alt-A to apply any zip from sd
6) Choose signed-dream_devphone_userdebug-ota-14721.zip (You won't see the entire filename)
7) When it is done it will ask you to reboot to complete the installation. Press Home+Back
8) You will be returned to the recovery screen in a few minutes, be patient.
9) Press Alt-A to apply any zip from sd
10) Choose update-cm-4.2.7.1-signed.zip
11) After the update is complete, hold Home and press Back to restart. (May take up to 15 minutes to boot)
12) Complete the setup process
Click to expand...
Click to collapse
iirc, his loader only lets you upgrade if you rename the files to update.zip. whats the one you are using that lets you preserve filenames?
xiton said:
iirc, his loader only lets you upgrade if you rename the files to update.zip. whats the one you are using that lets you preserve filenames?
Click to expand...
Click to collapse
If you can only apply "update.zip" you probably want to upgrade the recovery image
What recovery are you on?
Are you sure the phone is rooted and you're not at the stock recovery?
Either way give Cyanogen's Wiki a read, there's a lot more info there
http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_or_other_rooted_ROMs
jackslim said:
If you can only apply "update.zip" you probably want to upgrade the recovery image
What recovery are you on?
Are you sure the phone is rooted and you're not at the stock recovery?
Either way give Cyanogen's Wiki a read, there's a lot more info there
http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_or_other_rooted_ROMs
Click to expand...
Click to collapse
Thanks for all the info. I'm going to forward the info to him, since I'm not sure what he's running atm.
xiton said:
iirc, his loader only lets you upgrade if you rename the files to update.zip. whats the one you are using that lets you preserve filenames?
Click to expand...
Click to collapse
get the CM recovery here the update to this one here then you can apply any zip
yozpalang said:
please don't comment if you don't know what you are talking about
Click to expand...
Click to collapse
That's the OP asking for clarification because he's still lost
jackslim said:
That's the OP asking for clarification because he's still lost
Click to expand...
Click to collapse
sorry ,my bad
Needing some assistance as well.
The steps outlined on Cyanogen's wiki are dead simple. I followed them to the letter (save for installing the Hard SPL).
The problem is when my phone gets to the above listed step 11, it reboots and sits at the T-Mobile G1 logo. This is my second attempt to make the rooting/new mod changes and I let it sit at the logo for over an hour with zero change on the boot screen.
I have already installed the dreaimg.nbh, and I have DL's (3 times fro 2 different sources) the "signed-dream_devphone_userdebug-ota-14721.zip" and the "update-cm-4.2.7.1-signed.zip" and can use the 'apply any zip' option from the recovery menu.
The process itself seems to go fine (i.e. installing/formatting, blah blah blah) but the final reboot does nothing.
So, I am at a loss why apparently installed OS simply will not boot. Odd thing, is that I left my blue tooth headset on by accident and upon the last reboot, I hear it connect! It's almost as if it does boot up but will not change the screen.
I setup a second machine(Karmic Ubuntu) strictly for ADB but haven't the best clue on how to get it to work. While in the recovery menu I can issue "adb shell reboot" and the phone reboots but I cannot get the status. Even when trying "adb usb". Either I get 'device not found' or "connection closed" with either of those commands.(Not recalling which at the moment).
After this 'stuck on G1 logo', I can reboot and 'restore latest backup'(as noted in Cyanogen's steps) and the OS loads (although it is buggy as hell when trying to use any browsing, signal cuts in and out, drops carrier and gets it back.....severely annoying)
So....could use some real guidance.
As it stands:
OS: kila-user 1.0 TC4-RC29 115247 ota-rel-keys, release-keys
Recovery menu shows "Build: CyanogenMod v1.4 + JF" at the bottom.
Where to go from here?
Related
Edit: ****, ok so my phone isn't booting up now..the phone just freezes at the g1 splash logo.
I can still get into recovery console/bootloader, can I save my phone? Help!
I do have other theme's in /sdcard/themes/
I don't know if I can delete the current update.zip in my root and move one of them to the root and rename it, then flash that on? Someone please help!
-Ok so, I have the sdk...
-I'm in fastboot mode
-I have the correct driver for the phone, windows picks it up
but when adb doesn't pick up the devices, is there something I need to do to "get started" so to say? I'm trying to install some themes and push the browser.apk into the phone but, im stumped
tehseano said:
Edit: ****, ok so my phone isn't booting up now..the phone just freezes at the g1 splash logo.
I can still get into recovery console/bootloader, can I save my phone? Help!
I do have other theme's in /sdcard/themes/
I don't know if I can delete the current update.zip in my root and move one of them to the root and rename it, then flash that on? Someone please help!
-Ok so, I have the sdk...
-I'm in fastboot mode
-I have the correct driver for the phone, windows picks it up
but when adb doesn't pick up the devices, is there something I need to do to "get started" so to say? I'm trying to install some themes and push the browser.apk into the phone but, im stumped
Click to expand...
Click to collapse
First, you are at the wrong screen. You should not be in fastboot mode in the bootloader for updating themes, you should be in recovery mode.
I suggest you perform a wipe to possibly bring your phone back to normal at least. It can be done by turning off the phone, then pressing and holding the back and home button until you enter recovery mode.
From there press alt + w to wipe the phone.
Then restart by pressing back + home.
Next, before installing the theme, make sure its the correct one for your phone. Check with the author if it was made for RC30 or RC8, and if it is a non-wipe theme, because if it is not, you will be stuck at the Tmobile G1 splash screen (aka be in an indefinite loop) like your current situation.
If you are trying to install browser.apk (im assuming the multitouch browser - please correct me if im wrong) you will need to install JF 1.41 first. By default it will include the multitouch version of browser.apk
Please provide more information about your situation, and keep us posted.
andonnguyen said:
First, you are at the wrong screen. You should not be in fastboot mode in the bootloader for updating themes, you should be in recovery mode.
I suggest you perform a wipe to possibly bring your phone back to normal at least. It can be done by turning off the phone, then pressing and holding the back and home button until you enter recovery mode.
From there press alt + w to wipe the phone.
Then restart by pressing back + home.
Next, before installing the theme, make sure its the correct one for your phone. Check with the author if it was made for RC30 or RC8, and if it is a non-wipe theme, because if it is not, you will be stuck at the Tmobile G1 splash screen (aka be in an indefinite loop) like your current situation.
If you are trying to install browser.apk (im assuming the multitouch browser - please correct me if im wrong) you will need to install JF 1.41 first. By default it will include the multitouch version of browser.apk
Please provide more information about your situation, and keep us posted.
Click to expand...
Click to collapse
Sorry, I should have provided more information, and explained that the 2nd half of this post was my original post, which was just me asking how to correctly use ADB. I do already have JF 1.41, I upgraded yesterday. It wasn't my first theme I installed either. I was using Vintage War (for the Dream), but it hadn't been updated for 1.41, so I was trying the standalone apk adb push method found in this forum, which is where this post first oriented.
I was in recovery mode for installing themes, I'm using JF 1.41 RC30, with the HardSPL bootloader. Initially after installing the theme it would go blank after the g1 splash, so I had tried to install it again hoping it would fix it, unfortunately my thumb is a bit to fat and I hit alt W instead of S, anyways that is what put me into this infinite loop.
But like I said this wasn't my first time trying to mod the phone, I've had it rooted for a month or so now, and have been keeping up-to-date.
Any more information I can provide, please let me know. My phone is my livelyhood, I need it. So if anyone can help, the sooner would be better. Either way I am entirely greatful for any help anyone can provide. Thanks in advance!
tehseano said:
I was in recovery mode for installing themes, I'm using JF 1.41 RC30, with the HardSPL bootloader. Initially after installing the theme it would go blank after the g1 splash, so I had tried to install it again hoping it would fix it, unfortunately my thumb is a bit to fat and I hit alt W instead of S, anyways that is what put me into this infinite loop.
Click to expand...
Click to collapse
It is weird how a wipe caused you to go into an infinite loop. Which apk's did you try to push to your phone?
I would suggest to go without using the theme for now. JesusFreke had pointed out that some themes were causing problems for the new 1.41. update. You should check with the author of the theme to see if its compatible with the new 1.41 (which it should be since RC30 1.3, RC30 1.31, and RC30 1.41 are all compatible)
andonnguyen said:
It is weird how a wipe caused you to go into an infinite loop. Which apk's did you try to push to your phone?
I would suggest to go without using the theme for now. JesusFreke had pointed out that some themes were causing problems for the new 1.41. update. You should check with the author of the theme to see if its compatible with the new 1.41 (which it should be since RC30 1.3, RC30 1.31, and RC30 1.41 are all compatible)
Click to expand...
Click to collapse
....How do I get out of the loop. My phone doesn't get passed it. There has to be something I can do in console or recovery or something. I'm really sorry if I'm coming off as rude or demanding but I really need a phone, and I need it right now. I don't know what more I can tell you before someone can finally give me a solution (sorry)
1. Download RC29
2. Copy it onto your sdcard
3. Reboot your phone into the SPL with Power+Camera
4. When prompted, press the end key to start the reflash.
Note: this will completely wipe the flash chip on your phone and revert everything back to factory. You will need to re-root your phone and update to JF1.41
Next time, use nandroid to backup before installing themes, etc.
Datruesurfer said:
1. Download RC29
2. Copy it onto your sdcard
3. Reboot your phone into the SPL with Power+Camera
4. When prompted, press the end key to start the reflash.
Note: this will completely wipe the flash chip on your phone and revert everything back to factory. You will need to re-root your phone and update to JF1.41
Next time, use nandroid to backup before installing themes, etc.
Click to expand...
Click to collapse
Alright, I'm doing it now. And I did use nandroid and make a backup, no one said anything about how to restore it. Regardless thank you so very much, you are my Savior right now!
tehseano said:
Alright, I'm doing it now. And I did use nandroid and make a backup, no one said anything about how to restore it.
Click to expand...
Click to collapse
That's easy. Just grab a copy of the fastboot utility and the images off your sdcard in the 'nandroid' directory and boot your phone into the SPL. Plug your phone in via usb and press the back button once and you should see "Serial0" change to "FASTBOOT" Then open up a windows command prompt in the location of the exe you downloaded and run:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
fastboot reboot
Your phone will come back up with all of your applications, settings etc from when you did the backup. Keep in mind you need the HardSPL to do this though(look for three androids on skateboards in SPL). The G1 factory bootloader does not support fastboot, only NBH images that come from the factory.
Hi, my situation is a bit worse:
I have a Dev Phone, upgraded to JFv1.41.
Today, I got the pop up message telling me to do a "system holiday update 2 of 2". I press "Update now" and the phone got reboot. Since then... I could not get through the first screen that has the word "Android" at all, not even to the screen where Android icon is flashing. It just freezes right there.
The only way to turn off is to take out battery. I could not enter recovery mode through pressing Home+Power. One time, the screen actually turned into weird color patterns. Is there anything I can do? consider that I don't have any nandroid back up image at all?
I tried to download the DREAIMG-RC29.zip, unzip and copy to the sdcard, then reboot into the SPL with Power+Camera but nothing happens, just a 4 color screen said "serial0".
Thanks in advance.
Isn't the 4 color screen the standard bootloader that ships with retail G1's (not a dev phone bootloader)?
lugiamx said:
Hi, my situation is a bit worse:
I have a Dev Phone, upgraded to JFv1.41.
Today, I got the pop up message telling me to do a "system holiday update 2 of 2". I press "Update now" and the phone got reboot. Since then... I could not get through the first screen that has the word "Android" at all, not even to the screen where Android icon is flashing. It just freezes right there.
The only way to turn off is to take out battery. I could not enter recovery mode through pressing Home+Power. One time, the screen actually turned into weird color patterns. Is there anything I can do? consider that I don't have any nandroid back up image at all?
I tried to download the DREAIMG-RC29.zip, unzip and copy to the sdcard, then reboot into the SPL with Power+Camera but nothing happens, just a 4 color screen said "serial0".
Thanks in advance.
Click to expand...
Click to collapse
I had the same problem, almost verbatim. ADP1.1, JFv1.41, ran the Holiday update 1 of 2, no problems, did the 2 of 2 update, got stuck at the flashing Android boot screen. Pulled the battery, rebooted, same thing, waited 2-3 minutes at the flashing screen and was just about to pull the battery again and then all of a sudden the damn thing came to life, the OS loaded up and now everything's working fine. Gave me quite a scare.
ummm actually the fastboot utility wont work for my computer soo what shoud i do.... if anything i need a really good reply something long cause im new to this and my fone wont get off the android sign.
chinoman said:
ummm actually the fastboot utility wont work for my computer soo what shoud i do.... if anything i need a really good reply something long cause im new to this and my fone wont get off the android sign.
Click to expand...
Click to collapse
Why have you just hijacked a 5 month old thread? You haven't given use any details either. Fastboot is available for all OS's, it will work on your computer, you just probably don't know how to use it. Please make a new thread in the Q&A section where we can help you out there.
This should be closed or moved to Q&A.
hey man just unroot ur phone and root it again u soft bricked ur phone its ok
hey just try to unroot k
hey if u want me to fix it for u just email me at [email protected] and ill help u
I managed to root my phone by
http://forum.xda-developers.com/showthread.php?t=442480
applied the Hardspl.
However i did not complete the last step of
"First, choose a modified image from the list below:
ADP1.1: (md5: bacc58302e0b239d66c7bcc8db6c434b)
http://jf.odiness.com/v1.41/JFv1.41_...ronment.tar.gz
http://android-dls.com/forum/index.p...rb_v=viewtopic
http://andblogs.net/2009/01/jesusfre...mages-are-out/
RC33: (md5: f24b6c237775147cb4bc42efc2393973)
http://jf.odiness.com/v1.41/JFv1.41_...ronment.tar.gz
http://android-dls.com/forum/index.p...rb_v=viewtopic
http://andblogs.net/2009/02/new-rc33...om-jesusfreke/
RC8: (md5: de2d0d34adbb4015ee3aa5e4e7ca3c07)
http://jf.odiness.com/v1.41/JFv1.41_...ronment.tar.gz
http://android-dls.com/forum/index.p...rb_v=viewtopic
http://andblogs.net/2009/01/jesusfre...mages-are-out/
1. Download the image.
2. Rename it to update.zip.
3. Copy it to your phone's SD card.
4. Turn your phone off.
5. Start up in recovery mode by holding Home and pressing Power.
6. Press alt-W to wipe your device. (You need to do this, or the device may hang at the flashing Android screen)
7. Press alt-S to apply the update."
I skip the step as i thought those above apd 1.1, rc33, rc 8 were the outdated versions
Next i went to update to the latest radio and all was working fine.
Till I went straight to (http://forum.xda-developers.com/showthread.php?t=475381) and downloaded JFv1.50 ADP1.5 (post#2) and rename
to update.zip and alt-s to apply update.
Now my phone is stuck at the new blue andriod boot screen..
tried to flash back to ADP1.1: (md5: bacc58302e0b239d66c7bcc8db6c434b)
http://jf.odiness.com/v1.41/JFv1.41_...ronment.tar.gz but it doesnt allow me to at the /!\ with phone screen.
can any kind soul help me please?
When you see the "!" all you got to do is hit alt+l to bring up the list. Make sure you wipe before going to any build. Sometimes you have to give it some time especially since it's your first rom you've loaded, it can take awhile. Your not bricked.
lol problem solved..
wiped and reflashed jf's 1.51...
seriously scared the **** out of me..
I am very new at the whole root and rom process so i took the time to read through to forums to see if i could walk through it to get a rom.
When i tried to root my phone everything was okay, but when it was finished it said press the action key, instead of rebooting. when i pressed the action key it went back to the original screen and said serial0.
I went through all that because when i tried to install the rom, it said no signature and verification failed.
can some one help me fix this?
thanks in advance.
shockaj said:
I am very new at the whole root and rom process so i took the time to read through to forums to see if i could walk through it to get a rom.
When i tried to root my phone everything was okay, but when it was finished it said press the action key, instead of rebooting. when i pressed the action key it went back to the original screen and said serial0.
I went through all that because when i tried to install the rom, it said no signature and verification failed.
can some one help me fix this?
thanks in advance.
Click to expand...
Click to collapse
What ROM are you trying to install? It's a problem with the ROM most likely, not your phone.
shockaj said:
I am very new at the whole root and rom process so i took the time to read through to forums to see if i could walk through it to get a rom.
When i tried to root my phone everything was okay, but when it was finished it said press the action key, instead of rebooting. when i pressed the action key it went back to the original screen and said serial0.
I went through all that because when i tried to install the rom, it said no signature and verification failed.
can some one help me fix this?
thanks in advance.
Click to expand...
Click to collapse
It's hard to tell how far you got in the root process.. When you reboot into recovery (Home+Power) what does the screen look like?
Like the other poster said, it could be a problem with the ROM. But it could also be that you have the stock recovery image (which won't flash a modded ROM, since it is signed with the wrong keys).
i am trying to install the newest Cyanogen rom and i probably have the stock recovery img... how do i get a new one, i believe i downloaded my from http://forum.xda-developers.com/showthread.php?t=442480 but there is a possibility i didnt..
Not knowing where you are in the process of getting root, it's probably best to assume you don't have it, and go ahead and make sure your phone is fully rooted first. I read a few guides when I was starting - the first one that really made a lot of sense was Gizmodo's:
http://gizmodo.com/5146797/how-to-hack-android-for-multitouch-web-browsing-on-the-t+mobile-g1
Follow that, step by step. If any step doesn't react the way they say it will, you may need to start over. Once you finish that guide, you should be able to flash nearly any other ROM (other than Hero ROMs that need the "Danger" SPL - avoid until you study more).
After you've completed the guide for rooting, you can upgrade to the Cyanogen recovery (awesome because it lets you backup & restore your phone on the go, no PC needed) and CyanogenMod 3.6.5
Download this:
http://n0rp.chemlab.org/android/cm-recovery-1.3.1-signed.zip
Rename it to update.zip
Put it on the root of your SD card
Reboot into recovery (Home+Power)
Alt-S to flash it
Home+Back to reboot
Then download this:
http://n0rp.chemlab.org/android/update-cm-3.6.5-signed.zip
Rename it to update.zip
Put it on the root of your SD card (replace the last file we put there)
Reboot into recovery (home+power)
Alt-W to wipe
Alt-S to flash
Home+Back to reboot
Then you're all set. If you get lost at any point, just come back and tell us what's going on.
thanks Saiboogu. i got to the telnet, but when trying to connect to local host is says error while connecting to server error while receiving from server: null
shockaj said:
thanks Saiboogu. i got to the telnet, but when trying to connect to local host is says error while connecting to server error while receiving from server: null
Click to expand...
Click to collapse
OK - So you flashed DREAIMG.NBH, right? Go to Settings > About phone and scroll down to Build number - make sure it says RC29 somewhere in that string.
If that's right, just make sure you are launching telnetd correctly..
Press Home
Press Enter
Press Enter
type telnetd
Press Enter
You should wind up in your contacts searching for "telnetd" - if that's what you see, you probably did it right.
Then try the telnet client again. If that doesn't do it.. Sorry, I'm stumped. Hopefully someone else will chime in.
When i typed in [enter] [enter] telnetd [enter] nothing happens. it just remains as being searched...
also it is RC29
shockaj said:
When i typed in [enter] [enter] telnetd [enter] nothing happens. it just remains as being searched...
Click to expand...
Click to collapse
That sounds right -- All you'll see is the phone searching your contacts for telnetd, but if you did that exactly right, it should have run in the background. Then, run the telnet app on the phone and connect to localhost... Work this time?
Thanks that was the porblem.. i was able to get into the root and install the Cyanogen fine, but now that it is booting up the android screen tries to load then flickers, and it is stuck in this rotation....
That's a boot loop. Did that happen as soon as you installed CM3.6.5? Sounds like you need to flash again, maybe download and then flash again - sometimes the download can get corrupted. Also, make sure you wipe *first,* then flash. If you do it the other way, things can break.
nevermind i just wiped it again then reinstalled it and it worked, thanks so much for your help, i would have never finished this without yuo!
No problem at all, glad you got it. Now that you're all set, make sure you boot into recovery and perform a Nandroid backup - gives you lots of freedom to try things, knowing you can come back to a good working copy.
thanks thats great advice knowing me its only a matter of time!
Ok, so after using clockwork rom manager on my nook color and seeing how convenient it was, I thought, "hey maybe this would be good on my milestone." WRONG. I flashed the clockwork recovery (they even had an option for milestone) and when I rebooted into recovery from the software (either in rom manager or the reboot power option) it just rebooted straight into android. When I held the power and camera keys, it just took me to bootloader.
Under rom manager, there was also an option to flash the RA recovery, but that didn't seem to help (exact same behavior as clockwork recovery).
I'm currently running the CM7 mod and prior to this fiasco, I was using RA 1.7 (pretty sure). edit: RA 1.7 was my girlfriend's HTCmagic, I just remembered that I would have had some version of openrecovery on this phone.
So, I guess my question is, what are my next steps here? I'd really like to stop flying without a recovery. My only shred of an idea was to flash a stock image from rsdlite and set my milestone all the way back to stock and then reroot and re everything, but if someone has a better idea, I'd be very open to that as my plan seems like a big hassle.
A) not really the place for this post but anywa
B) you should beable to just flash the Vulnerable recovery http://android.doshaska.net/rootable then you can install a recovery from this forum thats for our phone!
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Tyfighter said:
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Click to expand...
Click to collapse
Quite alright if you have any more problems feel free to just PM me
Check this thread:
http://forum.xda-developers.com/showthread.php?t=1139120
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Tyfighter said:
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Click to expand...
Click to collapse
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
zacthespack said:
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Click to expand...
Click to collapse
what your doing (power + camera) is meant to put you into the bootloader mode... to get into recovery, hold 'x' on the physical keyboard and then hold the power button. This will get you into recovery. Hope this helps.
~D
are you sure that you did in fact flash the vulnerable bootloader, and not a newer, non-vulnerable one? sounds like that.. exploit fails, system reboots. also, if you are running an original rom right now, it does check the bootloader every reboot and flashes the non-vulnerable one!
Tyfighter said:
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
Click to expand...
Click to collapse
I'm a bit confused with how you're getting into Recovery mode, but the way to enter recovery is to hold Power + X, then Camera + Vol Up when you see the Motorola Logo.
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
EDIT: Despite RSD lite saying that the process as a success, the reflash did nothing.
Tyfighter said:
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
Click to expand...
Click to collapse
Where did you get the VR sbf? android.doshaska.net/rootable ?
Yep, that's the one.
EDIT: Finally got up the guts to load the official Telus sbf into RSD lite and pull the trigger. It seems like this is probably beyond salvage now. Once again, many thanks to everyone, and if all goes well, I hope to only be in the ranks of the unrooted/unmodded for a few minutes.
EDIT the second: Okay, so flash to stock went perfectly. Everything works, including recovery, but not openrecovery. I can get to the menu to flash the .zip, but it fails the esignature check. Which I'm assuming points to Vulnerable recovery not flashing correctly or perhaps my file is corrupt, or maybe something more exotic and exciting. I flashed SHOLS_U2_03.11.0 if that's relevant.
For those interested, everything is up and functional again.
I had to first flash back to stock, then flash the vulnerable recovery located at http://modmymobile.com/forums/downloads.php?do=file&id=28089 , then the standard, boot to recovery, blah blah blah, install a new rom.
Let this be a lesson to the rest of you; Clockwork Rom Manager does not, I repeat, does NOT seem to work on our milestones. Which is a real shame...
I realize this is a double post, but I'm just so darned jubilant to be able to update my rom again.
After having issues with the low 4GB memory of the myphone uno, i decided to try rooting the phone using some online instructions using Android One Toolkit. I ended up bricking it. Now when i turn on the phone, its stuck with the 4 animated circles.
I am a noob when it comes to android phones, but i do know how to install windows xp, vista, 7. I have used online instructions to clone my pc HD using clonezilla. I believe that if someone were kind enough to give step by step instructions on what files to download(like the original "OS" / "image") and where to get them. And how to use the software, i can get my myphone uno back to working order. So please anyone out there, can you help?
t-rayms said:
After having issues with the low 4GB memory of the myphone uno, i decided to try rooting the phone using some online instructions using Android One Toolkit. I ended up bricking it. Now when i turn on the phone, its stuck with the 4 animated circles.
I am a noob when it comes to android phones, but i do know how to install windows xp, vista, 7. I have used online instructions to clone my pc HD using clonezilla. I believe that if someone were kind enough to give step by step instructions on what files to download(like the original "OS" / "image") and where to get them. And how to use the software, i can get my myphone uno back to working order. So please anyone out there, can you help?
Click to expand...
Click to collapse
If you could tell us more clearly about what did you do actually and which instructions did you followed?
DNA_Uncut said:
If you could tell us more clearly about what did you do actually and which instructions did you followed?
Click to expand...
Click to collapse
i followed(or tried to) the instructions from the site of androidmtk with topic
"how to root android one devices easily"
sorry but system will not let me paste the actual link.
Process involved the use of android one toolkit.
and now my phone no longer boots. Stuck with those 4 animated circles. I have to remove the battery to get out of that screen. But no matter what i did, isn't there a way to just install android? Like installing windows on a blank hard drive? Start from scratch? Loss of data is not a factor
t-rayms said:
i followed(or tried to) the instructions from the site of androidmtk with topic
"how to root android one devices easily"
sorry but system will not let me paste the actual link.
Process involved the use of android one toolkit.
and now my phone no longer boots. Stuck with those 4 animated circles. I have to remove the battery to get out of that screen. But no matter what i did, isn't there a way to just install android? Like installing windows on a blank hard drive? Start from scratch? Loss of data is not a factor
Click to expand...
Click to collapse
Just follow the thread
http://forum.xda-developers.com/dream-uno/development/stock-rom-spice-dream-uno-mi498-t2915844
Download ROM (from the same thread)
http://forum.xda-developers.com/showpost.php?p=61588267&postcount=23
You should get back to stock kitkat (if you follow the instructions as explained). Once you get back your phone to working. Install ota updates you receive that will get you to stock 6.01
t-rayms said:
After having issues with the low 4GB memory of the myphone uno, i decided to try rooting the phone using some online instructions using Android One Toolkit. I ended up bricking it. Now when i turn on the phone, its stuck with the 4 animated circles.
I am a noob when it comes to android phones, but i do know how to install windows xp, vista, 7. I have used online instructions to clone my pc HD using clonezilla. I believe that if someone were kind enough to give step by step instructions on what files to download(like the original "OS" / "image") and where to get them. And how to use the software, i can get my myphone uno back to working order. So please anyone out there, can you help?
Click to expand...
Click to collapse
You don't need to go back on kitkat as DNA uncut says .....your device is running on which recovery ??
devil anand said:
You don't need to go back on kitkat as DNA uncut says .....your device is running on which recovery ??
Click to expand...
Click to collapse
im sorry but i dont know what "recovery" is. The phone is also no longer turning on so i cant get that info. But im ok with trying kitkat and if the flashing of the ROM works, at least ill have a working phone. And go from there and experiment some more to get the most out of the device.
When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see
---------- Post added at 03:58 AM ---------- Previous post was at 03:49 AM ----------
t-rayms said:
im sorry but i dont know what "recovery" is. The phone is also no longer turning on so i cant get that info. But im ok with trying kitkat and if the flashing of the ROM works, at least ill have a working phone. And go from there and experiment some more to get the most out of the device.
Click to expand...
Click to collapse
When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see
DNA_Uncut said:
Just follow the thread
http://forum.xda-developers.com/dream-uno/development/stock-rom-spice-dream-uno-mi498-t2915844
Download ROM (from the same thread)
http://forum.xda-developers.com/showpost.php?p=61588267&postcount=23
You should get back to stock kitkat (if you follow the instructions as explained). Once you get back your phone to working. Install ota updates you receive that will get you to stock 6.01
Click to expand...
Click to collapse
i installed the Android CDC Driver. DL the SP Flash Tool and the custom ROM. Rebooted the PC. Ran the SP Flash Tool. The final stage where i click on DL and connect my phone, nothing happens. The scrolling progress bar at the bottom of the flash tool doesnt start. With or w/o batteries in the phone. What do i do next?
devil anand said:
When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see
---------- Post added at 03:58 AM ---------- Previous post was at 03:49 AM ----------
When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see
Click to expand...
Click to collapse
when i selected the recovery option, the next screen is a picture of the android robot lying face up. With its body panel door open with red triangle with black exclamation markm, "No command" prompt
t-rayms said:
when i selected the recovery option, the next screen is a picture of the android robot lying face up. With its body panel door open with red triangle with black exclamation markm, "No command" prompt
Click to expand...
Click to collapse
First download a custom kernel zip (recommend thunderzap 5.1)
Then SuperSU 2.54 zip
Move this to files to your phones sd card
And again go to the menu which I told you during recovery (power and volume+ buttons at same time holding) then navigate to fastboot and enter ....you will se fastboot mode in the last line of the menu .
Now connect your phone to pc and open toolkit and press root.
You will see philz recovery loaded on your phone (philz recovery written on the top).
Then tap on wipe option and then factory reset and confirm it.
After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
Link - kernel- http://www.thunderzap.in/downloads/
SuperSU - https://download.chainfire.eu/741/SuperSU?_e_pi_=7,PAGE_ID10,5223979215
devil anand said:
First download a custom kernel zip (recommend thunderzap 5.1)
Then SuperSU 2.54 zip
Move this to files to your phones sd card
And again go to the menu which I told you during recovery (power and volume+ buttons at same time holding) then navigate to fastboot and enter ....you will se fastboot mode in the last line of the menu .
Now connect your phone to pc and open toolkit and press root.
You will see philz recovery loaded on your phone (philz recovery written on the top).
Then tap on wipe option and then factory reset and confirm it.
After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
Link - kernel- http://www.thunderzap.in/downloads/
SuperSU - https://download.chainfire.eu/741/SuperSU?_e_pi_=7,PAGE_ID10,5223979215
Click to expand...
Click to collapse
great. thanks. it worked. still cant believe it. But thank you very very very much.
t-rayms said:
great. thanks. it worked. still cant believe it. But thank you very very very much.
Click to expand...
Click to collapse
Just hit thanks!!
I went to Android mtk website ...then I knew where was the problem.
Note : SuperSU zip is used to root a phone via custom recovery (twrp,philzz) ...but in marshmallow you can't root your phone just by installing SuperSU zip ....you need to install a custom *kernel* first ....remember next time??
devil anand said:
Just hit thanks!!
I went to Android mtk website ...then I knew where was the problem.
Note : SuperSU zip is used to root a phone via custom recovery (twrp,philzz) ...but in marshmallow you can't root your phone just by installing SuperSU zip ....you need to install a custom *kernel* first ....remember next time
Click to expand...
Click to collapse
i take it that this step Then tap on wipe option and then factory reset and confirm it. fixed the bricking of the phone
and these steps After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
rooted the phone right?
One other thing is, whenever theres a system update, during the rebooting it does an error and i have to remove battery to restart the phone. Does rooting the phone cause updates not to work?
t-rayms said:
i take it that this step Then tap on wipe option and then factory reset and confirm it. fixed the bricking of the phone
and these steps After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
rooted the phone right?
One other thing is, whenever theres a system update, during the rebooting it does an error and i have to remove battery to restart the phone. Does rooting the phone cause updates not to work?
Click to expand...
Click to collapse
You took a bit ....if you have rebooted your phone after just factory reset .....you may have got bootloop again.....(stuck on boot animation).
About your second problem ....
When the error happens in between these steps of installation .......you tap on reboot and install and your phone goes to recovery and after successful installation your reboots .
What's the error ??
Yeah rooting your phone changes system which causes problem while installation of the original update...??
devil anand said:
You took a bit ....if you have rebooted your phone after just factory reset .....you may have got bootloop again.....(stuck on boot animation).
About your second problem ....
When the error happens in between these steps of installation .......you tap on reboot and install and your phone goes to recovery and after successful installation your reboots .
What's the error ??
Yeah rooting your phone changes system which causes problem while installation of the original update...
Click to expand...
Click to collapse
i get the prompt about an update ready for install, i click on it, it does the prompt to reboot so i choose to reboot. During the rebooting it tries to install updates, then the robot image comes up with the word "error". Stuck there until battery is removed. Afterwards the phone will turn back on.
t-rayms said:
i get the prompt about an update ready for install, i click on it, it does the prompt to reboot so i choose to reboot. During the rebooting it tries to install updates, then the robot image comes up with the word "error". Stuck there until battery is removed. Afterwards the phone will turn back on.
Click to expand...
Click to collapse
Just unroot your phone and try updating again !!!??
devil anand said:
First download a custom kernel zip (recommend thunderzap 5.1)
Then SuperSU 2.54 zip
Move this to files to your phones sd card
And again go to the menu which I told you during recovery (power and volume+ buttons at same time holding) then navigate to fastboot and enter ....you will se fastboot mode in the last line of the menu .
Now connect your phone to pc and open toolkit and press root.
You will see philz recovery loaded on your phone (philz recovery written on the top).
Then tap on wipe option and then factory reset and confirm it.
After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
Click to expand...
Click to collapse
It worked for me too, but now I can`t update SuperSU.
Update from OS failed, from TWRP gives bootloop.
I`m on CM13 SNAPSHOT.
... also front camera cant take picture, but preview works ok.
Johnny_16 said:
It worked for me too, but now I can`t update SuperSU.
Update from OS failed, from TWRP gives bootloop.
I`m on CM13 SNAPSHOT.
... also front camera cant take picture, but preview works ok.
Click to expand...
Click to collapse
What's the need of updating SuperSU ..,...
Use Google camera ....
Sent from my A1 using XDA-Developers mobile app
t-rayms said:
i get the prompt about an update ready for install, i click on it, it does the prompt to reboot so i choose to reboot. During the rebooting it tries to install updates, then the robot image comes up with the word "error". Stuck there until battery is removed. Afterwards the phone will turn back on.
Click to expand...
Click to collapse
You've root? And which update do you wanna install on your phone!?
Just tell me what's your build number.. I'll help ya out.
HELP
My cousins Myphone Uno is not turning on when pressing the power button, but if I put in a charge the screen turns on after a few minutes showing the battery but I don't know if it is charging. after a minute the display will go out and the screen flashes a once or twice then off and screen turns on and display the battery it will be on a loop, I can still get to boot option when screen flashes starts,
it shows:
[Recovery Mode]
[Fastboot Mode]
[Normal Boot]
[Normal Boot +ftrace]
[Normal slub debug off]
but when I select any options or not to ,the phone will turn off. Can you help me find a way to make this phone work again? thank you in advance!
PS: If I connect it in my PC it wasn't detected and the the loop will go on and on.
Usb debugging mode is also turned off