Related
I've been doing some searching around but am unable to find a definite answer to my questions regarding the recovery. Following the Non-Tmobile 32B instructions for installing Cyanogen, I have flashed Amon_RA 1.6.2G as my recovery image and I am not in any way unhappy with this, just curious.
As per the instructions, prior to flashing the Amon_RA recovery permanently to the phone, I made a nandroid backup. If I were to restore this backup, would the stock recovery image be restored?
In the case of the answer being no I have been searching for the file for the stock recovery image with little success. Many people asking for it, seemly noone getting it. So where is it? Does anyone have it or can point me to where to get it?
After digging further I downloaded a file meant for the Google ION device (signed-google_ion-ota-150275.zip) out of pure curiousity, which has the same SPL as my device. Taking a peek inside the archive there is a recovery.img file in there. Is this the same recovery image that was stock on my phone? If not, how does it differ?
I know there are a lot of questions there, but after 2 days of forum reading and searching and countless google searches my questions have built up to this point. The answers just don't seem to be right there (maybe the blondeness is to blame), and I'd like to know that I can undo everything that has been done, just in case of needing repairs to whatever.
If anyone has the answers I will be most appreciative.
If you install the OTA ROM from your carrier, it will install the custom recovery and and basically revert all changes made since the day you set your hands on that phone.
A lot of people have to send in their phones for warranty and that's the quickest way to revert it.
There are instructions for T-Mobile US at:
http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
You can use them except use your carriers sappimg.nbh
Mo0oSaH said:
If you install the OTA ROM from your carrier, it will install the custom recovery and and basically revert all changes made since the day you set your hands on that phone.
A lot of people have to send in their phones for warranty and that's the quickest way to revert it.
There are instructions for T-Mobile US at:
http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
You can use them except use your carriers sappimg.nbh
Click to expand...
Click to collapse
Thanks for that but it looks like that file is totally useless to my phone, as I said above I'm looking for the image for my provider/country/whatever. I would imagine that the build number would be different in some way (correct me if I'm wrong) to the vodafone one and thus would be a bit of a mistake to claim warranty and have them find Tmobile stuff on it.
But thanks so much for the link, it's reassuring to see that the process could be rather painless, so long as I get the right files in the end. I'll cross my fingers that some clever person has what I'm searching for and it magically appears in my inbox one day lol
alliekhat said:
Thanks for that but it looks like that file is totally useless to my phone, as I said above I'm looking for the image for my provider/country/whatever. I would imagine that the build number would be different in some way (correct me if I'm wrong) to the vodafone one and thus would be a bit of a mistake to claim warranty and have them find Tmobile stuff on it.
But thanks so much for the link, it's reassuring to see that the process could be rather painless, so long as I get the right files in the end. I'll cross my fingers that some clever person has what I'm searching for and it magically appears in my inbox one day lol
Click to expand...
Click to collapse
The problem is that you're probably trying to flash the T-mobile 32B SAPPimg.nbh to your vodafone. You need the vodafone SAPPimg.nbh. Put it on your SD card, power down your phone, hold the volume and power buttons at the same time until your phone powers on. It should take you to a white screen and load the nbh file. It will ask if you want to proceed with the update. Just confirm and let the update COMPLETE FULLY. This nbh file will return you to 1.5 stock cupcake, but from here you will be able to receive OTA updates from your provider. Hope it helps.
http://forum.xda-developers.com/showthread.php?t=580631
You will find the Vodafone nbh link at the top of this thread.
sombionix said:
The problem is that you're probably trying to flash the T-mobile 32B SAPPimg.nbh to your vodafone.
Click to expand...
Click to collapse
I'm not trying to flash anything, like I said in my first post, I'm happy with what I have done to my phone, I'm running cyanogenmod and have no intention of going back to stock unless I have a problem.
I'm just trying to find answers. Namely the fact that I have a nandroid back up of prior to flashing the new recovery and am wondering if restoring this will replace the recovery with the stock one, and whether the recovery images are all the same no matter where they come from.
I guess I missed this over the weekend and I am looking for the original install that I dont need to have root for. I have been reading over the threads here and in the Dev forum and I am not seeing any links to the download for Non-Root users.
I am to much of a ***** to root my phone. i spent way to much cash on it and i am too worried something will go wrong.
So here is want I am asing for
A. The original non root install with instructions on how to do it
or
B. Someone to help walk me through the process of rooting and getting FroYo 2.2 set up on my phone.
Please shoot me a PM if your willing to help out. I am just way to worried if I do this without someone who knows what they are doing I am going to screw up my phone, and my wife would never let me buy another one ...lol
Can somsone help out a fellow Dev, thanks
Sorry I can't post links but here you go
androidandme.com/2010/05/news/how-to-manually-install-android-2-2-on-your-nexus-one/
Ya just found it buried in a thread
Thanks
See if I would have spent another 10 minutes searching I would have found it without having to ask ...lol
Got to remember to scan threads for 30 minutes not 20 before asking ...lol
Or use this: http://forum.xda-developers.com/showthread.php?p=6043779#post6043779
(Or the Root/2.2 links in my sig.)
Okay, I'll give you the general idea, as I understand it:
The FRF50 ROM that was leaked from Google is exclusively for ERE27 Builds only. Unless that is the native build on your phone, you will not be able to apply that as is.
Paul O'Brien, over at Modaco, repacked it so that it can be flashed with any current ROMs. Though he's said that there are no conditions, there in fact are a few stipulations to be aware of.
-If you have never unlocked your bootloader, you won't be able to flash anything at all. Something to think about. There's a few threads here dedicated to this topic alone. It voids your warranty so that is why some people are holding off and waiting for the official OTA update to be released.
-Though it's true that you don't have to be rooted to flash Paul's repack, unless you have ERE27 stock, you need to flash using one of the custom recovery images. And in order to flash your recovery.img, you need to be rooted. So you need to have had rooted before.
So the steps, from stock, would be:
(1) Unlock your bootloader, via flashboot.
(2) Flash superuser to your boot.img (aka rooting)
(3) Flash a custom recovery to recovery.img (I use RA)
(4) Flash Paul's FRF50 repack using said recovery image.
I'm sorry I can't post the links to the relavant posts, but my status as a member doesn't allow me to. Hope this helped clear some things up for you.
Paul22000 said:
Or use this: http://forum.xda-developers.com/showthread.php?p=6043779#post6043779
(Or the Root/2.2 links in my sig.)
Click to expand...
Click to collapse
Paul, is that Avatar a picture of YOU?
OMG theres a search feature!!!
Really OMG I didnt know this!
I guess me saying I searched threads and the site for 20 minutes was something you missed.
But thanks to all who actually decided to help and not be another one of these "USE SEARCH" people.
I respect the work you do for us here Paul, but come on man. Read before making a post like that ....lol
attn1 said:
Paul, is that Avatar a picture of YOU?
Click to expand...
Click to collapse
All I wil say is:
λ
LOL ...........
you don't need to root to install froyo and you don't need to hook up your nexus to a pc. my method is pretty simple and it works.
edit: I shouldn't say it's my method. Its actully a backdoor to installing froyo.
theletterj said:
Okay, I'll give you the general idea, as I understand it:
The FRF50 ROM that was leaked from Google is exclusively for ERE27 Builds only. Unless that is the native build on your phone, you will not be able to apply that as is.
Paul O'Brien, over at Modaco, repacked it so that it can be flashed with any current ROMs. Though he's said that there are no conditions, there in fact are a few stipulations to be aware of.
-If you have never unlocked your bootloader, you won't be able to flash anything at all. Something to think about. There's a few threads here dedicated to this topic alone. It voids your warranty so that is why some people are holding off and waiting for the official OTA update to be released.
-Though it's true that you don't have to be rooted to flash Paul's repack, unless you have ERE27 stock, you need to flash using one of the custom recovery images. And in order to flash your recovery.img, you need to be rooted. So you need to have had rooted before.
So the steps, from stock, would be:
(1) Unlock your bootloader, via flashboot.
(2) Flash superuser to your boot.img (aka rooting)
(3) Flash a custom recovery to recovery.img (I use RA)
(4) Flash Paul's FRF50 repack using said recovery image.
I'm sorry I can't post the links to the relavant posts, but my status as a member doesn't allow me to. Hope this helped clear some things up for you.
Click to expand...
Click to collapse
Okay, there's a lot of good info out there mixed in with a lot of mis-information.
Your steps will work BUT:
I prefer to do it this way:
Unlock the boot loader via fastboot
Flash Amon_RA 170 recovery for Nexus One
Do a nandroid Backup
Flash your ROM of choice (Modaco's FROYO in this case)
If you are running stock recovery, you CAN flash, but only Google's updates. If you have a T-mobile N1 this may work for you without unlocking the bootloader by flashing the Google Froyo Release with the stock recovery:
Google Froyo Release
You must be on release ERE27 for this to work.
Here's a link to some instructions on how to use the stock recovery program:
jp_macaroni's thread
I suspect that since most people have already rooted or cannot get to ERE27, Paul's guide is the best way to go for them.
If you are running a custom recovery, you can flash custom updates, but NOT Google's updates intended for any stock phone/firmware level.
You don't need to root (root access) to the current ROM before flashing a custom ROM. You only need to unlock the bootloader and install a custom recovery image.
jcohenlv said:
OMG theres a search feature!!!
Really OMG I didnt know this!
I guess me saying I searched threads and the site for 20 minutes was something you missed.
But thanks to all who actually decided to help and not be another one of these "USE SEARCH" people.
I respect the work you do for us here Paul, but come on man. Read before making a post like that ....lol
Click to expand...
Click to collapse
Yeah you know, everyone is new once. It's easy to sort out the tripe from the real deal when you've been around the block once or twice. Paul is doing his best to be helpful and not cause more confusion.
The problem isn't that people can't search so much as it is that searches yield too much conflicting information, so lets not jump down people's throats when they ask for a point of clarification. Instead, lets start asking moderators to sticky good info and pulling redundant/bad info so that searches are more meaningful. The number of new threads in here because of the Froyo release is mind numbingly high. Let's all try to exercise some patience.
attn1 said:
Okay, there's a lot of good info out there mixed in with a lot of mis-information.
Your steps will work BUT:
I prefer to do it this way:
Unlock the boot loader via fastboot
Flash Amon_RA 170 recovery for Nexus One
Do a Nadroid Backup
Flash your ROM of choice (Modaco's FROYO in this case)
If you are running stock recovery, you CAN flash, but only Google's updates. If you have a T-mobile N1 this may work for you without unlocking the bootloader:
If you are running a custom recovery, you can flash custom updates, but NOT Google's updates intended for any stock phone/firmware level.
You don't need to root (root access) to the current ROM before flashing a custom ROM. You only need to unlock the bootloader and install a custom recovery image.
Click to expand...
Click to collapse
I'm not disagreeing with you, but as far as I know, yes, you do have to root in order to flash Amon_RA Recovery to your phone. If that's not correct, I apologize for spreading misinformation.
theletterj said:
I'm not disagreeing with you, but as far as I know, yes, you do have to root in order to flash Amon_RA Recovery to your phone. If that's not correct, I apologize for spreading misinformation.
Click to expand...
Click to collapse
You only need to unlock the bootloader. You do not need root.
Unlocking the boot loader allows installation of an alternate recovery, which allows you to install custom software to the existing ROM or to install a custom ROM. It's updating the ROM that allows you to gain root access, not unlocking the boot loader. It goes in this order:
> Unlock boot loader (void warranty - still not rooted)
> Install custom recovery
> nandroid backup (recommended/optional)
> Update ROM (for root access - or not)
The original instructions worked perfect
All that was needed was to change the name to update.zip load it on the root of the SD card then but the phone in bootloader and load recovery from SD.
Took about 5 minutes.
Once the phone came up it did a few things and took about another 5 minutes to chill on the processes then I was able to use the phone without any problems.
So for those interested here are the exact steps:
This is for NON Rooted T-Mobile Version!!!!
To manually install Android 2.2 on the Nexus One, perform the following steps:
1. Download the official Android 2.2 firmware for the Nexus One.
2. Copy the file to your microSD card and name it update.zip (newb warning: not update.zip.zip)
3. Power off your phone.
4. Hold down the VOLUME DOWN button and power it back on.
5. The phone will now search for files like PB00IMG.zip, etc. This is normal. Scroll down to recovery (using Volume Down Key) and press the POWER button.
6. When you see the “/!\” symbol, press the POWER button and the Volume Up button at the same time. You should be presented with a menu and one of the options should be “Apply sdcard:update.zip”.
7. Use the trackball to navigate to “apply sdcard:update.zip” and select it.
8. When you see “Install from sdcard complete”, select “reboot system now”.
Wait 5 minutes, phone will reboot once rebooted let the phone sit for about 5 minutes then you are good to go. It couldn't be any easier
HellllOOooOoOo!!
Ok, here goes. First off, I searched. A lot. There is so much conflicting information and opinions out there. I hate to annoy you pros with noob-ness but I have to. Sorry!
Here is the quick version:
Friend gave me an Atrix 4G. He is big on experimenting, rooting, custom ROMs and all that. I am not. At all. I want to use it on t-mobile. I DO get a signal and can text. MMS doesn't work and motoblur wont let me set up an account. This results in no access to email other then Gmail. Basically, I want to bring the phone back to its original (or close as possible) state. Hopefully, that will solve some of my issues.
-Android Version
2.3.4
-Unlocked
-Rooted
-Build Number
olympus_hktw-userdebug 2.3.4 4.5.2A-5_OLH-3110614 test-keys
-Clockwork recovery mod installed (if that matters)
I am not THAT tech savvy but can follow instructions well. I've already been messing around but cant seem to get RSD Lite to actually flash properly. I dont care for customs ROMS, hacking and tinkering. I just want this phone to work as well as possible.
Can anyone give me some personal assistance? Please? Step by step would be great. I'll be refreshing this page often in hopes of responses.
Vul said:
HellllOOooOoOo!!
Ok, here goes. First off, I searched. A lot. There is so much conflicting information and opinions out there. I hate to annoy you pros with noob-ness but I have to. Sorry!
Here is the quick version:
Friend gave me an Atrix 4G. He is big on experimenting, rooting, custom ROMs and all that. I am not. At all. I want to use it on t-mobile. I DO get a signal and can text. MMS doesn't work and motoblur wont let me set up an account. This results in no access to email other then Gmail. Basically, I want to bring the phone back to its original (or close as possible) state. Hopefully, that will solve some of my issues.
-Android Version
2.3.4
-Unlocked
-Rooted
-Build Number
olympus_hktw-userdebug 2.3.4 4.5.2A-5_OLH-3110614 test-keys
-Clockwork recovery mod installed (if that matters)
I am not THAT tech savvy but can follow instructions well. I've already been messing around but cant seem to get RSD Lite to actually flash properly. I dont care for customs ROMS, hacking and tinkering. I just want this phone to work as well as possible.
Can anyone give me some personal assistance? Please? Step by step would be great. I'll be refreshing this page often in hopes of responses.
Click to expand...
Click to collapse
It sounds like you need to set up a proper T-Mobile APN. (you have a T-Mobile SIM card currently installed?)
If you can get on Wifi, try to go the the Play store and download Tweakker or other APN utilities that enter the APN for your based on your carrier.
co.ag.2005 said:
It sounds like you need to set up a proper T-Mobile APN. (you have a T-Mobile SIM card currently installed?)
Click to expand...
Click to collapse
Yes. I have a t-mobile SIM card installed. My concern is what the previous owner may have done and whatever ROM is loaded on this phone. Can I somehow bring it back to stock or get a super stable, close to stock as possible ROM first and then start addressing the quirks I have?
Is this an AT&T branded phone? I'm not sure if getting back to stock is necessary, and if you do get back to stock, you might be SIM locked to AT&T (I could be wrong however). If you want to flash a fresh, stock ROM but still be rooted, SIM unlocked, etc., find a 2.3.6 Fruitcake in this forum or try NottachTrix 4G ROM.
however, I'd wait till others weighed in before doing anything. Honestly, I'd try getting your APN (download Tweakker app and walk through the steps) going now and if that solves your issue, your ROM might be working fine for you... my $0.02
oh, and welcome to XDA!
Vul said:
Yes. I have a t-mobile SIM card installed. My concern is what the previous owner may have done and whatever ROM is loaded on this phone. Can I somehow bring it back to stock or get a super stable, close to stock as possible ROM first and then start addressing the quirks I have?
Click to expand...
Click to collapse
1. Download the fruitcake .zip you want (webtop also, if you want it)
2. Do a full wipe with fastboot (search if you're unsure how to)
3. Boot into recovery and flash the .zip you downloaded from step 1
4. Reboot and you're done
This will put you back to stock. I can't remember if fruitcakes are pre-rooted, but if not you can easily root again.
Alright, now we're getting somewhere.
co.ag
The phone itself says "unlocked" upon startup. I got the network unlock code direct from AT&T because at first the phone wouldn't even recognize my t-mo SIM. Phone is now network unlocked.
Ghost
gonna search now for fruitcake and see what thats all about. Do I need webtop?
Then going to get fastboot. Guess I dont need RSD Lite anymore?
Im doing this because I dont know what the previous owner has done and would like a clean slate. Kind of like changing the oil on a used car you buy, even if the PO says it was done.
Ok so,
I found fastboot with recovery tool and the .exe files within the ZIP dont do anything.
The fruitcake ZIP file I downloaded according to your link, I'm not sure what to do with that. lol
Help?
**am I supposed to be saving these files to the phone itself? If so, where? Internal storage? SD card?
Vul said:
Alright, now we're getting somewhere.
co.ag
The phone itself says "unlocked" upon startup. I got the network unlock code direct from AT&T because at first the phone wouldn't even recognize my t-mo SIM. Phone is now network unlocked.
Ghost
gonna search now for fruitcake and see what thats all about. Do I need webtop?
Then going to get fastboot. Guess I dont need RSD Lite anymore?
Im doing this because I dont know what the previous owner has done and would like a clean slate. Kind of like changing the oil on a used car you buy, even if the PO says it was done.
Click to expand...
Click to collapse
that "unlocked" bit on start up means your bootloader is unlocked, doesn't have anything to do with the SIM card. All this means is that you can flash a ROM since the phone is "unlocked"
Vul said:
Ok so,
I found fastboot with recovery tool and the .exe files within the ZIP dont do anything.
The fruitcake ZIP file I downloaded according to your link, I'm not sure what to do with that. lol
Help?
**am I supposed to be saving these files to the phone itself? If so, where? Internal storage? SD card?
Click to expand...
Click to collapse
the fruitcake .zip goes on your internal sdcard. BUT, before you start doing anything, please go through the stickied threads in this section and read up on how to flash ROMs to your phone. This will include how to wipe your phone using the fastboot commands and how to flash the fruitcake .zip.
start here, read this post
http://forum.xda-developers.com/showthread.php?t=1154600
then follow guides to
"HOW TO INSTALL FRUITCAKES ON 2.3.4 (GREAT SBF/RSD ALTERNATIVE!!!)"
and
"ROMs & Kernels:
FYI:
Before installing any ROM or Kernel I suggest you do the following to help prevent error, boot-loops, etc. Also, it's a good idea to flash a new ROM or Kernel on a fully charged device:
1) Download which ever ROM or Kernel you plan on flashing and have the .zip on your device ready to flash.
2) Backup your apps (not system data), contacts, etc. Also consider making a CWM backup of your device, just in case.
3) Boot into CWM Recovery
4) Wipe Dalvik Cache (under advanced in CWM)
5) Wipe Cache Partition
6) Wipe data/factory reset
6a) If you're using ROM Manager/CWM you will need to reboot the device after step 5, and upon reboot enter fastboot mode and enter the command: "fastboot -w" or "moto-fastboot -w" if you prefer using moto-fastboot. Then type "fastboot reboot" and upon reboot make sure to enter Android Recovery again, so that you can flash the ROM/Kernel.
7) Install .zip from SD Card (choose the .zip you wish to install)
8) If you installing a radio, theme, kernel, etc. on top of a ROM, I would suggest redoing the whole wipe process again between flashes.
9) Reboot the Device
- If you get a boot loop, try entering Android recovery and re-wiping the chace and data, and perhaps try reflashing the ROM/Kernel. Or if you made a CWM backup, you can always restore that."
Vul said:
Ok so,
I found fastboot with recovery tool and the .exe files within the ZIP dont do anything.
The fruitcake ZIP file I downloaded according to your link, I'm not sure what to do with that. lol
Help?
Click to expand...
Click to collapse
Ok, sorry I wasn't that detailed in my other post and assumed you were on your phone (my bad). First things first, read the N00b guide.
1. Anytime you download CWM .zips, put them on the root of your phone's sdcard. You'll need them there in order access them from recovery. ( note: sdcard=internal sd card & sdcard-ext=external sd card for blur ROMS )
2. Fastboot commands are executed from the command line. Open a command prompt and navigate to the directory containing fastboot.exe in order to use it. The Noob guide should have links to all the fastboot commands you'll need.
3. With the Atrix's unlocked BL, holding Volume Down when turning the phone on will bring up a series of bootmodes to choose from. This is how you get into fastboot, recovery, RSD, etc. Navigate through the choices with Volume Down. Select one by pressing Volume Up. You should only ever really need Fastboot and Android Recovery.
4. CWM is used to flash .zips (ROMS, kernels, apps) while in recovery mode. Use romracer's to make things easier on yourself later.
Read through the N00b guide and this will all make perfect sense.
I have no idea what Im doing. I think because this phone has been tampered with so much already, it's making it extra tough to work with.
I managed to install CM7. Its the only ZIP file that actually seemed to take. I still dont understand fastboot , in the sense that I don;t know when Im supposed to see a command prompt. Also, now, CM7 is asking me to upgrade to premium and I have to pay for it. There doesnt seem to be a free way of installing it so that I can sync all my info through my google account. Ugh. Im not cut out for this but Ive been screwing with this literally since 730 this morning.
**CM7 with google apps packet installed. So far, so good. Im happy with this considering its pretty close to stock gingerbread, kinda like my G2. Now, Im hopefully done messing around. Would be nice if they release a solution for the fingerprint scanner or if I can get my gmail to auto sync but at least I can stop obsessing for the time being. Great help guys, thanks so much!!!!
I've read the threads that returned when i typed my title and they all have caveats and/or problems I've encountered before., e.g., bootloop, etc. or I've rooted phones before and with TWRP or CWM recovery, you can flash a stock ROM, but the phone will still be "modified" and then you have those problems.
Q: Is it possible to return the device back to stock form in entirety (I don't care if "tampered message appears) I just want a stock recovery, stock system to be able to take OTA (or lack thereof.).
The roots I've down in the past suggest that once TWRP or CWM is installed, they're there forever. Is this incorrect?
I bought this X Play with a horrible ROM that I hate.
If I just flash a stock ROM, then I'll still have to deal with possible OTAs that may cause problems, but if I'm not rooted, then I can take thew safely. I think
I may have answered my own question.
Thanks in advance for any help
Yes. You absolutely can return to stock.
http://forum.xda-developers.com/moto-x-play/general/guide-how-to-flash-factory-image-return-t3261486
Keep in mind that the when you get to the fastboot command procedures, they are wrong. Surprisingly it still hasn't been updated with the correct procedures.
Go to the 4th page of that thread: http://forum.xda-developers.com/mot...-to-flash-factory-image-return-t3261486/page4
Look for the post by @dev>null that says correct fastboot procedure.
FanDroid09 said:
Yes. You absolutely can return to stock.
http://forum.xda-developers.com/moto-x-play/general/guide-how-to-flash-factory-image-return-t3261486
Keep in mind that the when you get to the fastboot command procedures, they are wrong. Surprisingly it still hasn't been updated with the correct procedures.
Go to the 4th page of that thread: http://forum.xda-developers.com/mot...-to-flash-factory-image-return-t3261486/page4
Look for the post by @dev>null that says correct fastboot procedure.
Click to expand...
Click to collapse
Thanks again for pointing me to that thread. It worked great.
And a warning for anyone (like I was) downgrading stock, this is vital or you'll hard brick: http://forum.xda-developers.com/moto-x-play/general/reminder-how-to-downgrade-6-0-to-5-1-1-t3267253
Hi. I'm just gonna say this first: I didn't know entirely what I was doing when beginning this operation. I was just trying to do something fun and new, and it didn't pan out. I fully acknowledge that I am an idiot.
Now, the story. I was attempting to root my LGV20 with this guide: https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 .
I have read over this thread more times than countable and thought I was doing everything correctly. I got to the "STEP3.BAT" portion of the guide and long story short, my phone crashed during it and somehow got foobarred.
It *kinda* works (as in it will boot for around a minute) and then blue/black screen into a reboot.
Is there any way I can save this phone? Hard resets, going into software, more dumb computer stuff, anything. I don't *need* to get this phone working again but it would be really preferable.
Simultaneously I fully accept the responsibility in failing the operations. I know that somewhere I must have messed up. If no-one wants/ can help me, tell me so. Just means new phone time.
If any more detail on what happened is needed, tell me.
First off: that guide is ONLY for the H910 (AT&T) variant, so make sure with your model
and also, when you said a "blue or black screen" it also has very small writings too, right? If so, then you may have faced a kernel/bootloader panic
Technically your phone is *still* alive, and your best method is to start over again, assuming if you read the whole guide carefully then you have backed up your firmware and can still access download mode.
Flash your stock firmware back (or use the H915 firmware provided by the guide), wipe and setup your phone again, then root the phone again.
I also suggest replacing the TWRP recovery inside the provided Dirtysanta folder cuz that's what i did when i faced the kernel panic
MEMO#22 said:
First off: that guide is ONLY for the H910 (AT&T) variant, so make sure with your model
and also, when you said a "blue or black screen" it also has very small writings too, right? If so, then you may have faced a kernel/bootloader panic
Technically your phone is *still* alive, and your best method is to start over again, assuming if you read the whole guide carefully then you have backed up your firmware and can still access download mode.
Flash your stock firmware back (or use the H915 firmware provided by the guide), wipe and setup your phone again, then root the phone again.
I also suggest replacing the TWRP recovery inside the provided Dirtysanta folder cuz that's what i did when i faced the kernel panic
Click to expand...
Click to collapse
Thanks so much. Freaked out over this for a good bit. Came back, did what you said and we're back at that step fully working. Life saver.
Now my first guess as to why step3 failed is that i didn't have the latest version of TWRP. How can I set that up?
Inside the root package folder you can see an .img file named twrp 3.0.2-1- us996.img
What i did was downloaded a later version
(not latest cuz my phone won't boot at the latest version for some reason), copied the name of the original twrp and renamed it, paste it to the folder, overwrite the old one, and try to root it again
MEMO#22 said:
Inside the root package folder you can see an .img file named twrp 3.0.2-1- us996.img
What i did was downloaded a later version
(not latest cuz my phone won't boot at the latest version for some reason), copied the name of the original twrp and renamed it, paste it to the folder, overwrite the old one, and try to root it again
Click to expand...
Click to collapse
Alright, i've done that now too. Thanks. Is there anything else i should/need to keep in mind to ensure failure is not going to happen? I want to make 100% sure I get everything right this time.
reptarien said:
Alright, i've done that now too. Thanks. Is there anything else i should/need to keep in mind to ensure failure is not going to happen? I want to make 100% sure I get everything right this time.
Click to expand...
Click to collapse
No i don't think there is more things to do, the guide you're following is pretty much straightforward already.
100% guarantee is always a stretch here in XDA. But if you're still facing problems you can ask for help on that guide's thread.
MEMO#22 said:
No i don't think there is more things to do, the guide you're following is pretty much straightforward already.
100% guarantee is always a stretch here in XDA. But if you're still facing problems you can ask for help on that guide's thread.
Click to expand...
Click to collapse
I really want to give up on this. This time I successfully made it through all Step 3, but I also noticed that my screen was kind of glitched and not rendering properly at that stage. After it rebooted, I unplugged my micro usb cable and it gave me an angry green warning message I will attach here.
If you/someone can tell me what to do with this message from here or instruct me on how to flash stock H910 10 q back onto the phone without doing TWRP (since i'm evidently incapable of installing it) I would be most appreciative.
Slightly better picture without anything cut off.
reptarien said:
I really want to give up on this. This time I successfully made it through all Step 3, but I also noticed that my screen was kind of glitched and not rendering properly at that stage. After it rebooted, I unplugged my micro usb cable and it gave me an angry green warning message I will attach here.
If you/someone can tell me what to do with this message from here or instruct me on how to flash stock H910 10 q back onto the phone without doing TWRP (since i'm evidently incapable of installing it) I would be most appreciative.
Click to expand...
Click to collapse
The screen glitching is normal, the green text after boot however is somehow not.
Sad to hear that it still didn't work, there something seems to be interrupting the process of rooting your phone. I dunno if it has something to do with ARB (anti rollback) preventing you to root
If you want to go back to your stock firmware that you backed up, you can:
-Carefully flash each file of your backed up firmware through adb and fastboot mode
-build a zip file of your firmware and flash through TWRP (since it didn't succeed tho)
MEMO#22 said:
The screen glitching is normal, the green text after boot however is somehow not.
Sad to hear that it still didn't work, there something seems to be interrupting the process of rooting your phone. I dunno if it has something to do with ARB (anti rollback) preventing you to root
If you want to go back to your stock firmware that you backed up, you can:
-Carefully flash each file of your backed up firmware through adb and fastboot mode
-build a zip file of your firmware and flash through TWRP (since it didn't succeed tho)
Click to expand...
Click to collapse
Could you reply with any links with a tutorial on how to do the first thing? Or describe it. Sorry for being so dumb i'm a total newbie lol
reptarien said:
Could you reply with any links with a tutorial on how to do the first thing? Or describe it. Sorry for being so dumb i'm a total newbie lol
Click to expand...
Click to collapse
Unfortunately i can't find any guides when it comes to flashing the back up.
I did read something back then on turning it into a zip file, but even if you can build one you still need TWRP, in which case you haven't successfully installed, so that's no option
Flashing the backup files requires specific commands, especially to the part on what partition should it be flashed to
When LGUP backs up your phone's firmware, you can see a vast number of files(i can't remember how were they named, I'll look up a reddit post about it)
The files where named based on what partition it came fom (H910_modemxx_COM12, H910_system_COM12 or something like that)
These are image files, what i did as far as i can remember was rename these files by adding an IMG extension for ADB to recognize
Flash them according to it's partition name:
"Fastboot flash system H910_system_COM12.img"
"Fastboot flash recovery H910_recovery_COM12.img'
Etc.
To go to fastboot, turn off your phone and hold the volume down button , then plug your phone to the PC.
But i really cannot guarantee this, because for all i know, in order to flash this you need fastboot, and to get fastboot you need to root your phone, because only the engineering bootloader has it (i'm sorry if it's wrong tho), and flashing these files to fastboot might be a bit dangerous because it will not verify the files, there may be chances that you might flash a corrupted file. so flashing via LGUP is the safest option so far if you don't know what you're doing