Related
I'm a relatively new user to root, with my htc hero cdma rooted since Feburary 2010, but I've been having some problems as of late with my custom recovery image.
When I try to load the Image from fastboot, I get the error "Wrong or no image," (Among others of the same nature), as fastboot tries to load the image several times, it fails with the same general error. It happens very quickly, so I can't post many details, but if a picture or two is needed for more information, I can provide a few for refrence. I am running Darchdroid 2.6.2, great rom, and I would love to update to the newest image(And Rom). I've tried booting into recovery several times, but it bootloops at the HTC logo. I've tried booting from fastboot and DS updater, but the same bootloop occurs, probably because the error is ongoing at fastboot. I've tried flashing multiple images and from using flashrec, I get a command line error. I've flashed many through command line, and the same error occurs.
Can Anyone help me out, or knows what's going on?
PS: If it helps, I have all of the fastboot device stock, EX: radio is the stock 1.0.4 and the touch panel is the stock touchpanel, etc.
put a new recovery image on your Sdcard.
Code:
adb remount
adb shell
flash_image recovery /sdcard/recovery.img
See what that does for ya.
Broken Root???????
Kcarpenter said:
put a new recovery image on your Sdcard.
Code:
adb remount
adb shell
flash_image recovery /sdcard/recovery.img
See what that does for ya.
Click to expand...
Click to collapse
I tried it, but unfortunately, it didn't work. Instead, the same error came up again several times, and I tried with many different images, even with my last two working images.
Can you ask or message anyone who you know who might know whats going on, and can help me???
Ryoma Echizen said:
Can you ask or message anyone who you know who might know whats going on, and can help me???
Click to expand...
Click to collapse
What error message is it giving when you try to flash a new image?
I would also try a different SD card.
EDIT:
NVM I assume that you are getting the run via adb error.
Try a different card. Your current ROM should have absolutely no effect on nandroids.
Broken Root???????
Kcarpenter said:
What error message is it giving when you try to flash a new image?
I would also try a different SD card.
EDIT:
NVM I assume that you are getting the run via adb error.
Try a different card. Your current ROM should have absolutely no effect on nandroids.
Click to expand...
Click to collapse
Ok I will try it, thanks. That could be the problem, since I switched sd cards recently. I am not getting the run via adb error, I am getting an error on fastboot that says; wrong or no image. My image started to freeze when I tried to flash when I switched sd cards to an 8gb. I will try this, and thanks a lot. I probably wouldn't have thought of this way of solving the problem!
Broken Root???????
Welllll.......
I still can't get the image to work...
Can you give me any help, like direct message anyone who you know who might know how to solve this problem??? The error is as follows: "finding name of image, some element in the said image,"
"Wrong or no image!"
Can you message zenulator or anyone who you know who might be experienced in this problem.
Kcarpenter said:
put a new recovery image on your Sdcard.
Code:
adb remount
adb shell
flash_image recovery /sdcard/recovery.img
See what that does for ya.
Click to expand...
Click to collapse
Do this:
Code:
adb remount
adb shell
cd \sdcard\
flash_image recovery recovery.img
Thats actually what I always have to do for some reason the other does not work.
Broken Root???????
For some reason, I get the same error.
Here are some more specific details (my approximate translation because it went by so fast, and not even the full 15 or so lines, but the gist of it...) :
Checking sdcard...
Opening HCTDIAG.zip...
No image!
checking HCTDIAG.nhb...
Wrong or no image!
If you think the log would help, I can email or message it to you. I have been trying all kinds of commands for the last three hours, and no luck...
If anyone knows any solution to my problem, it would be a great help...
ADB works fine, anyway, so I don't think that's the problem.
Broken Root???????
Anyways, if it helps, I'm just trying to get back to the damagecontrol 2.1 stock sprint leaked rom. I might be able to get away with a wipe and then leaving the only data on my sdcard as the backup from the stock sprint leaked. I don't mind any method, as long as I can get back to default and sense, I'll even take the official update with the low ram of 40 mb, rather then 80.
Best advice right now is to start over. Run the ruu, then reroot. It only takes fifteen minutes at most. I know you probably don't want to but sometimes you gotta instead of wasting hours
Broken Root???????
There may be one error though...
When I try to install apks (I have a mac), I get the error as follows, ex: can't find Browser.apk to install.
Maybe has to be in the operating system area, not sdcard?
Anyways, forget about this. I just need to get a working recovery image. Any advice on how to access recovery via adb, like maybe, "reboot recovery" though I doubt this will work, considering that it is just another way to boot into my broken recovery mode w/out an image, or the apparent, "wrong image!"
Broken Root???????
How do I do this, since I am running a rom that doesn't have htc sync??? Should I factory data reset and place a backup folder w/stock sprint 2.1 leaked on the sdcard so the boot will retrieve that and boot that data, since the whole operating system is extracted onto that backup? I don't really know how to run ruu's, and I don't want to run the risk of bricking my phone.
(Running darchdroid 2.6.2, and I do not blame darch for my current situation, just trying to avoid any misunderstandings there.) (O.O)
Broken Root???????
Sorry about the situation I'm in. Definitely the worst possible situation, and I really, really appriciate any help that anyone is willing to provide me.I'm clearly in a sticky situation...
go here and download the sprint hero 2.27.651.5 ruu. You need htc sync get that from sprint site in support and downloads. First run the sync then run the ruu exe with your phone plugged in and usb debugging turned on. Actually just follow the root guide from regaw
I found another way, it worked for me:
http://forum.xda-developers.com/showpost.php?p=6879703&postcount=953
Just realized you were on MAC I don't know much bout that but I have heard you can dualboot it with windows. Definitely something you want to do if you can and plan on messing with android
-------------------------------------
Sent via the XDA Tapatalk App
Broken Root???????
Well, I do have a windows vista laptop.
However, the sprint support section of the site is down for repairs, (TT.TT) so I can't download htc sync for the moment...
Broken Root???????
YESSSSSSS
The clockwork recovery option worked!!!
Special thanks to davec1234 for providing a working solution!!!
Thanks to thatguydid for providing another solution, and thanks to everyone who has replied to my problem that I created this thread to solve.
Just in case anyone else has this problem, then try clockwork recovery, and I think that Rom Manager is a great app from the market that helped me fix my problem, as well as improve my device speed and fixed my permissions to slow down force closes.
THANKS TO EVERYONE ON XDA WHO PARTICIPATES AND MAKES THIS FORUM GREAT!!!
I couldn't ever have fixed my problem without everyone's help!!!
STAY AWAY from GOD SPEED
i thought it was cool but it wouldnt let me flash new recoverys and froze phone after nandroideds on cm6... i also think it wouldnt let me flash the newest zen exp but im testing the above posts method
I'm been searching the Nexus One Q&A section for an answer to my problems, but I couldn't find a solution. I'm running a stock version of 2.3.3 on my phone. It's never been rooted, and I have never rooted a device as well. I'm entirely new to this and have no idea what I'm doing. My device has no warranty but I'm still concerned about it. Again, I have no experience at all.
Also, I don't know if I would want to unlock the bootloader as I could lose everything. If there is a way to retain everything reliably (I don't know if those back-up applications are the most effective) that would be convenient.
So, can anyone help me root my virgin Nexus One?
Thanks for your time,
Tread Fox
Mybackup pro backs up apps and data. After you root you can use titanium backup. Also smsbackup and restore for your SMS :]
Alright, that's re-assuring. But what about actually rooting the phone?
Hmm I can't help with rooting because I have an Evo, just sharing some backup knowledge :/
You can use this threads wiki for the N1 and the stickies here:
http://www.nexusoneforum.net/forum/nexus-one-development-hacking/
You need to read several guides until you get a good idea of what you are doing and why.
Use the apps mentioned above to back up your phone info, once rooted you can do a complete and immediate phone backup of everything, like a full image pc backup.
If you do the one-click method, make sure it is for you OS, you will be limited in some things you can do, like fastboot commands and will be unrooted if you dl OTA's.
Read, Read, Read!!!
Before you flash a rom read the op page carefully and the last 20 pages for tips, info, issues etc.
Ken
This works for 2.3.3?
EDIT: So my only options are to unlock the bootloader or roll back? Which do you recommend?
You probably saw this in XDA wiki for N1:
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root
I would unlock, more options as you get more into flashing and you can't be unrooted by Google OTA's.
This is good guide for the S, but you can glean steps and maybe better understanding for the process. At the bottom in related posts is a root guide. I like the steps, but things like the fastboot and superuser may not be for the N1. However you can find them online. Just an easy to understand guide.
http://jaxov.com/2011/02/install-android-2-3-3-gingerbread-on-nexus-one-manually/
TreadFox said:
This works for 2.3.3?
EDIT: So my only options are to unlock the bootloader or roll back? Which do you recommend?
Click to expand...
Click to collapse
Sorry man, just got your message (phone died on me, and I've been playing with my other toys anyway...)
Yes, your options are to unlock the bootloader or roll back.
Both options will lose all date, so you need to backup either way.
My preference is to unlock the bootloader, but I can understand why people may not want to. Unlocking the bootloader can effect any warranty that's remaining on the phone (the phone has a 1 year warranty, no matter who owns it).
Thanks for all your help guys. Does anyone have a specific guide for rolling back? I don't need or want a custom rom, just setcpu...
Read my signature, execute PASSIMG method with FRG33. if it doesn't work (and sometimes it doesn't) - you're out of luck.
TreadFox said:
Thanks for all your help guys. Does anyone have a specific guide for rolling back? I don't need or want a custom rom, just setcpu...
Click to expand...
Click to collapse
This is how to go back to FRG33: http://forum.xda-developers.com/showpost.php?p=11745519&postcount=21
But if I were you, I would just unlock your bootloader. Makes life easier.
I'll unlock the bootloader. I saw a guide on the nexusoneforums on how to do this. But it's about a year old. Is there anything that's changed?
I'm sorry I'm being indecisive, I'm trying to take suggestions from anybody!
TreadFox said:
I'll unlock the bootloader. I saw a guide on the nexusoneforums on how to do this. But it's about a year old. Is there anything that's changed?
I'm sorry I'm being indecisive, I'm trying to take suggestions from anybody!
Click to expand...
Click to collapse
No, nothing has changed. You need to have the Android SDK set up properly. Then just boot into the bootloader by holding down the trackball while pushing the power button. Then open a command prompt in the directory where the fastboot.exe file is (probably C:\Program Files\Android\android-sdk-windows\tools) then just type: fastboot oem unlock
Follow this to set up the, it's easier (just the first post):
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA Premium App
I don't know what I'm doing. This is confusing. When I hook up the phone to the pc it says its found new hardware. I'm running XP. What do I do? I think I'm going over my head with this. Also, how do I make sure mybackup will work? I don't want to lose my stuff!
TreadFox said:
I don't know what I'm doing. This is confusing. When I hook up the phone to the pc it says its found new hardware. I'm running XP. What do I do? I think I'm going over my head with this. Also, how do I make sure mybackup will work? I don't want to lose my stuff!
Click to expand...
Click to collapse
If you feel like you are in over your head, you probably are, and have not done enough reading. I just looked at danger-rat's post in the link he provided, and it seems quite straight forward, no? He even tells you how to install the drivers. "Step #3" under "To install the drivers" in the first post TELLS you that windows will detect new hardware and will ask you to install a driver. What seems to be the problem?
I did, and nothing happened. At all. I asked for it to download files from usb driver. Nothing happened at all. Is it something I'm doing wrong?
I have the SDK file on my desktop, I have all of the files inside that are needed. When the computer asks me to download the drivers, I re-direct to the usb driver folder located in the SDK which is located on my desktop. The computer claimed installation was successful, but nothing happened. When I try clicking the fastboot.exe in the tools file, it immediately forcecloses. Is it my pc? Is it the file? Is it the phone? I did read the material and so far nothing has helped.
TreadFox said:
I did, and nothing happened. At all. I asked for it to download files from usb driver. Nothing happened at all. Is it something I'm doing wrong?
I have the SDK file on my desktop, I have all of the files inside that are needed. When the computer asks me to download the drivers, I re-direct to the usb driver folder located in the SDK which is located on my desktop. The computer claimed installation was successful, but nothing happened. When I try clicking the fastboot.exe in the tools file, it immediately forcecloses. Is it my pc? Is it the file? Is it the phone? I did read the material and so far nothing has helped.
Click to expand...
Click to collapse
Well, after you have installed the driver that the computer asked you to install. That's just the driver needed to sync your file and stuff on your sd card. The other driver and adb setup is needed to actually access your phone.
So I asked for it to install the wrong files? What files do I install? Because from that guide it said point to usb driver. I'm only following the guide like you all asked, and nothing happened.
You don't launch fastboot by clicking on it windows.
Sent from my Nexus One using XDA App
Finally ready to root my phone, decided I am ready for some extra features and roms. Few concerns
1. The biggest one is how are so many people deleting there entire storage? Is it simple to do? I just don't want to make the mistake
2. Debating between aio or using adb commands just to know how to do it.
3. Never used aroma...how user friendly is it?
This isn't my first time, started rooting on my G1, but I just cannot get Linux down and been on Samsung for a while
Thank you been reading htc one threads and just trying to do it right and not need to use your guys amazing troubleshooting
I followed the information used here: http://forum.xda-developers.com/showthread.php?t=2244060
Unlocking the bootloader did, sadly, reset my phone to factory default, erasing my music, downloaded apps, custom ringtones & such. There may be a way to prevent that, but I didn't look into it too much prior to rooting. Plus, I had the music and ringones backed up to my PC. Anyway, the instructions at the aforementioned link are quite thorough, and very easy to follow. I used adb and flashed TWRP; no Aroma involved. The whole process took me about 15 minutes, once I stopped trying to do it with my Windows 8 laptop (with USB 3.0) and used one with Windows 7 and a USB 2.0 port. Afterwards I flashed Tranquil One.
Not worried about losing stuff during unlock process, but seen a lot of people wiping everything later and having to use adb sideload or ruu.
Don't want to be the guy in a day asking for help because I messed up
But I do know not to load anything but sprint roms and kernels
Here's what I did, if it helps:
1. Downloaded and extracted the package in the link posted above.
2. Unlocked the bootloader.
3. Installed TWRP via adb, both of which were included in the extracted files from number 1.
4. Did a backup in TWRP, so I'd at least have a restore point as close to factory settings as possible. It'll come in handy if I have to take the phone in for service at some point. Just restore the image and re-lock bootloader.
5. Copied that backup to my PC.
6. Downloaded Tranquil One ROM, copied to my phone, did factory reset in TWRP & flashed the ROM.
Honestly, if you're even slightly comfortable doing this and you know how to follow instructions you shouldn't end up being "that guy" asking for help after the fact. The one way I can see it becoming more involved is if you're running Windows 8 and/or using USB 3.0. Drivers can be really irritating.
I think they fixed the windows 8 problem. I had no problems on it. Windows 8 reads this one but not my lte for some reason. But again no problems on the ONE.
Sent from my HTCONE using xda app-developers app
Hello, everyone, I'm in a bit of a bind here.
I own an HTC One on Sprint's network and have decided tonight to finally root it. I unlocked the bootloader and successfully installed TWRP Recovery v.2.6.3.0. (downloaded from here: http://techerrata.com/browse/twrp2/m7wls) I ran into a bit of an issue, though, when trying to install Paranoid Android (Which I had downloaded from here: http://forum.xda-developers.com/showthread.php?t=2315236); it was saying it couldn't mount my sd card. Note that the HTC One doesn't have any external storage, so it meant the internal one. And it also said something along the lines of "some symlinks failed," my apologies that I can't be more specific.
Anyway, I had my phone all backed up (Important files such as photos, audio files have already been backed up with Dropbox, so no concern there) and I read that it was a problem with TWRP after version 2.3.3.0. So I tried to install that recovery, but it didn't stick. So I tried switching to Clockworkmod Recovery, which I downloaded from here: http://www.clockworkmod.com/rommanager. I scrolled down to HTC One (Sprint) and selected the classic 6.0.3.6.
All was well, I backed up again, until I tried to install PA again. I had the same basic issue. Long-story short, in between the switching recoveries, I had forgotten to restore my data before I switched recoveries, so I lost the backup and I'm 99% there is no OS on my phone at the moment.
I've heard that I can, using TWRP (which I flashed back to), sideload a ROM onto my phone to flash. I tried this, however it had be check that my device was attached by typing "adb devices" in the command prompt (open in the folder where adb.exe is), and no devices are listed.
It appears that there's a loading bar on my phone when i click ADB Sideload, and it says "Starting ADB sideload feature...", however, nothing seems to be happening.
Any help would be super greatly appreciated, and I'm sorry if I left out any information.
Rooting my old Moto Droid was easy, but something was bound to get messed up i guess
The first problem I see is the link for PA is not from the Sprint forum.
Sen me a PM i can get you fixed up
If he does t get you fixed all up I can help you out also but he is a smart one so I'd imagine he will get you up and going. Either way, possibly the greatest partial thread title ever... "Mistakes may have been made"
bigdaddy619 helped me considerably, thank you He got me back to basically having a new, store-bought phone. Which was much better than I had!
Just time to start over, I suppose, and not make any mistakes. I definitely was using a Paranoid Android for the Samsung Galaxy Nexus and didn't realize it (Though my main mistake was flashing a new recovery before restoring my backup. Rookie mistake!)
Uh oh, well all you need to know is what I have always said is if you root, ALWAYS S-Off in order to undo your mistakes no matter what and that will almost always kep you safe.
Sent from my HTCONE using Tapatalk 4
I once ended up with wiped internal storage, could not get my computer to load correct driver for adb so I flashed ruu then redid rooting process, s-off, etc
Sent from my Nocturnal Google Edition CDMA 5.0 using XDA Premium 4 mobile app
So my computer bit the dust about two months ago so i found myself in a situation where yes, I had a PC back when i unlocked the bootloader, ran ADB fastboot commands and flashed the twrp recovery.img . But now, I have no access to computers whatsoever. So heres what I did:
Downloaded - Str8upx's TWRP backup found here - http://forum.xda-developers.com/showpost.php?p=67914526&postcount=43
Nightbreed813s flashable MM rom for Sprint Phones found here - http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
After downloading the files, I extracted the TWRP backup from the .zip file, navigate with a file explorer past the folder with a Serial Number on it, copied the backup folder that comes next, moved it to my external sd cards TWRP backup folder .
Then I booted into TWRP, after backing up my current ROM, wiped everything and then flashed the sprint ROM
after that, I restored ONLY the System portion of Str8upx's backup. (this means i didn't flash the system image either, ONLY SYSTEM)
Rebooted phone and I was done. Still had SuperSU, but had to install busybox.
I'd like to note that from this point on everything works without any problems and I'm on the official Metro MM. The red letters show up every time I boot the phone now, instead of only when i boot into TWRP like it used to so please be aware of that. Also, my baseband and kernel appear to be different than the ones in Metro MM. I do intend on updating once somebody makes a TWRP flashable version of MM. But until then, i'll stay on this as my daily driver as again, everything does work. I figured I'd share what I learned and maybe we will see less threads about " i tried to install MM on my rooted 626s and it failed " feel free to ask any questions if there are any. All thanks goes to Nightbreed813 and Str8upx for uploading the files. If you have a second and you use these files, Click thanks on the linked posts to thank them.
I need to make all aware that wifi isn't going to work with this method. So if you plan on using wifi, you're gonna have to flash the ruu. Full disclosure I no longer stand behind this due to lack of wifi. I went ahead and flashed with the RUU and fastboot flashed twrp back. This solution was only a temporary fix for me. As it should be for anybody if its used at all
You reckon this'll work with Boost Mobile?
TeamLiquid.koyo said:
You reckon this'll work with Boost Mobile?
Click to expand...
Click to collapse
There's already a flashable MM ROM for the boost 626s, http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
Yeah. On boost that's all you need
Genius... Simply Genius
talksickisil said:
So my computer bit the dust about two months ago so i found myself in a situation where yes, I had a PC back when i unlocked the bootloader, ran ADB fastboot commands and flashed the twrp recovery.img . But now, I have no access to computers whatsoever. So heres what I did:
Downloaded - Str8upx's TWRP backup found here - http://forum.xda-developers.com/showpost.php?p=67914526&postcount=43
Nightbreed813s flashable MM rom for Sprint Phones found here - http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
After downloading the files, I extracted the TWRP backup from the .zip file, navigate with a file explorer past the folder with a Serial Number on it, copied the backup folder that comes next, moved it to my external sd cards TWRP backup folder .
Then I booted into TWRP, after backing up my current ROM, wiped everything and then flashed the sprint ROM
after that, I restored ONLY the System portion of Str8upx's backup. (this means i didn't flash the system image either, ONLY SYSTEM)
Rebooted phone and I was done. Still had SuperSU, but had to install busybox.
I'd like to note that from this point on everything works without any problems and I'm on the official Metro MM. The red letters show up every time I boot the phone now, instead of only when i boot into TWRP like it used to so please be aware of that. Also, my baseband and kernel appear to be different than the ones in Metro MM. I do intend on updating once somebody makes a TWRP flashable version of MM. But until then, i'll stay on this as my daily driver as again, everything does work. I figured I'd share what I learned and maybe we will see less threads about " i tried to install MM on my rooted 626s and it failed " feel free to ask any questions if there are any. All thanks goes to Nightbreed813 and Str8upx for uploading the files. If you have a second and you use these files, Click thanks on the linked posts to thank them.
Click to expand...
Click to collapse
I downloaded the Metro pcs RUU onto a PC to install the update, then fast boot flashed twrp. (At this moment it didn't show the red warning letters In the bottom of the boot screen) I suspect it happened when I flashed the SuperSU.zip
i2andog said:
Genius... Simply Genius
Click to expand...
Click to collapse
Thanks man. Lol....
Did you try? If so, any issues?
IsaacGuti said:
I downloaded the Metro pcs RUU onto a PC to install the update, then fast boot flashed twrp. (At this moment it didn't show the red warning letters In the bottom of the boot screen) I suspect it happened when I flashed the SuperSU.zip
Click to expand...
Click to collapse
I really don't know what causes the red letters. Personally speaking, I can still manage with or without them.
talksickisil said:
Thanks man. Lol....
Did you try? If so, any issues?
Click to expand...
Click to collapse
No I have a working PC... I just really admired your use of magiver like resources
Gotcha. . Yeah, it's not the first time. And not just phones. I Jimmy rig my way thru a lot of life haha. To be honest I'd probably still do this even if I had my PC. I'm just not a fan of fastboot and adb commands. And I don't want to lock my bootloader again
Yes.. those mother f'in boot loaders would burn in hell if I had any say ... in uh.. boot loaders souls or whatever... ... *crickets*.... hey check that out
Sent from my HTC Desire 626s using Tapatalk
talksickisil said:
So my computer bit the dust about two months ago so i found myself in a situation where yes, I had a PC back when i unlocked the bootloader, ran ADB fastboot commands and flashed the twrp recovery.img . But now, I have no access to computers whatsoever. So heres what I did:
Downloaded - Str8upx's TWRP backup found here - http://forum.xda-developers.com/showpost.php?p=67914526&postcount=43
Nightbreed813s flashable MM rom for Sprint Phones found here - http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
After downloading the files, I extracted the TWRP backup from the .zip file, navigate with a file explorer past the folder with a Serial Number on it, copied the backup folder that comes next, moved it to my external sd cards TWRP backup folder .
Then I booted into TWRP, after backing up my current ROM, wiped everything and then flashed the sprint ROM
after that, I restored ONLY the System portion of Str8upx's backup. (this means i didn't flash the system image either, ONLY SYSTEM)
Rebooted phone and I was done. Still had SuperSU, but had to install busybox.
I'd like to note that from this point on everything works without any problems and I'm on the official Metro MM. The red letters show up every time I boot the phone now, instead of only when i boot into TWRP like it used to so please be aware of that. Also, my baseband and kernel appear to be different than the ones in Metro MM. I do intend on updating once somebody makes a TWRP flashable version of MM. But until then, i'll stay on this as my daily driver as again, everything does work. I figured I'd share what I learned and maybe we will see less threads about " i tried to install MM on my rooted 626s and it failed " feel free to ask any questions if there are any. All thanks goes to Nightbreed813 and Str8upx for uploading the files. If you have a second and you use these files, Click thanks on the linked posts to thank them.
Click to expand...
Click to collapse
But what i'm wanting to know is, did you flash the standard or the De -Bloated rom? I'm not clear on that. Also are there any differences in the UI or OS that you noticed in this mm update?
s3llz said:
But what i'm wanting to know is, did you flash the standard or the De -Bloated rom? I'm not clear on that. Also are there any differences in the UI or OS that you noticed in this mm update?
Click to expand...
Click to collapse
As far as which sprint ROM you flash debloated version or regular it doesn't really matter, since once you restore the twrp backup you're going to be on the standard non debloated metro official MM. As far as UI differences, there's a few things here and there. Nothing mind blowing. What was advantageous for me is the expanded internal storage. I love it.
I tried installing with the RUU and always got error 155 all the time some I am trying this method out. I would like to know will this method still work on a phone with exposed binary, and for those with MetroPCS, does the service still work as well.
Hello I tried doing everything as followed installed the sprint now after every call or just randomly i get "SIM card has been inserted" "Select a carrier" which T-mobile is the only one to work. Then after a call and again randomly i get this message again and have to repeat the process. Does anyone know why and how can I fix this?
bnawolf said:
Hello I tried doing everything as followed installed the sprint now after every call or just randomly i get "SIM card has been inserted" "Select a carrier" which T-mobile is the only one to work. Then after a call and again randomly i get this message again and have to repeat the process. Does anyone know why and how can I fix this?
Click to expand...
Click to collapse
In my instructions you don't stay on the sprint rom. You're supposed to restore the backup after installing that rom. But I need to make all aware that wifi isn't going to work with this method. So if you plan on using wifi, you're gonna have to re lock your bootloader and flash the ruu