Related
so i decided to root my phone today, and flash a custom rom. i am using the t-mobile variant.
i used the all in one toolkit to unlock bootloader, and everything was going good, but i think i might have forgot to install superuser? i am not sure what went wrong. but i was trying to flash android revolution hd, and it was stuck in the bootloop. so i thought i needed to flash the boot.img like i had to in past devices. did that, but still nothing.
i go into CWM and now i can't access the sd card. so i did a wipe and it still won't mount on my computer. did a little reading around, and someone suggested relocking the bootloader, and flashing stock recovery file (i don't think i got the right one), and then unlocked the bootloader and reflash CWM, and that sideloading a rom would work. everytime i try to sideload a rom, i get a device not found error, but fastboot responds to other adb commands. i did make a backup in CWM, but i moved it from the phone to my laptop, but i have no idea how to even use it. adb push to device does nothing. =/
i really really really hope i didn't brick my phone. anyone have some insight? help? i tried looking for a RUU but it seems there isn't one for t-mobile.
so i am able to flash recovery, and get into it, when i try to mount sdcard in the options, it doesn't say anything. stuck in bootloop still. can't sideload. can't push. really really wish it had an external sd card which would make issues like this a bit easier to solve.
Nah, mods don't delete threads like this. Thread moved to T-Mobile HTC One Q&A (and don't post questions anywhere other than the Q&A section in the forum of your device's variant )
fastboot won't respond to adb commands because it's fastboot not adb. i would use the toolkit and install TWRP recovery and load up TWRP. from there you can adb sideload or do other adb commands once you get it loaded.
orvon.freeman said:
I advise this due to the fact you can use adb commands.
relock bootloader then run an RUU here is the one from AT&T http://forum.xda-developers.com/showthread.php?t=2287036&highlight=ruu.
Click to expand...
Click to collapse
Do not attempt to flash an AT&T RUU to your T-Mobile device. In the best case scenario, it should fail(due to S-ON). I would not recommend fooling around with RUUs on different carrier-branded devices.
As for the OP, I'm not sure what to recommend. Most internal storage-only devices won't mount in USB. Wiping your internal storage was the worst thing that you could have done. I'm not sure why adb sideload won't work if normal adb commands and fastboot commands are being accepted. Have you tried a different USB port? I know it sounds strange, but sometimes that can make a difference.
unremarked said:
Do not attempt to flash an AT&T RUU to your T-Mobile device. In the best case scenario, it should fail(due to S-ON). I would not recommend fooling around with RUUs on different carrier-branded devices.
As for the OP, I'm not sure what to recommend. Most internal storage-only devices won't mount in USB. Wiping your internal storage was the worst thing that you could have done. I'm not sure why adb sideload won't work if normal adb commands and fastboot commands are being accepted. Have you tried a different USB port? I know it sounds strange, but sometimes that can make a difference.
Click to expand...
Click to collapse
just thought about that. Each carrier is diff my bad. good catch unremarked.
I looked for a nandroid that you could use with the toolbox to flash it is t-mobile http://forum.xda-developers.com/showthread.php?t=2182823
orvon.freeman said:
this is the wrong section for this. This belongs in QA not dev. Next time read the rules http://forum.xda-developers.com/showthread.php?t=2158147
Good luck
Click to expand...
Click to collapse
pandaball said:
Nah, mods don't delete threads like this. Thread moved to T-Mobile HTC One Q&A (and don't post questions anywhere other than the Q&A section in the forum of your device's variant )
Click to expand...
Click to collapse
appreciate it, xda forums sure has grown since when i was on here with my g2/my4g slide, lots of subforums, and in a haze of having soft bricked my phone, i posted in the wrong section. sorry!
TygerByte said:
fastboot won't respond to adb commands because it's fastboot not adb. i would use the toolkit and install TWRP recovery and load up TWRP. from there you can adb sideload or do other adb commands once you get it loaded.
Click to expand...
Click to collapse
unremarked said:
Do not attempt to flash an AT&T RUU to your T-Mobile device. In the best case scenario, it should fail(due to S-ON). I would not recommend fooling around with RUUs on different carrier-branded devices.
As for the OP, I'm not sure what to recommend. Most internal storage-only devices won't mount in USB. Wiping your internal storage was the worst thing that you could have done. I'm not sure why adb sideload won't work if normal adb commands and fastboot commands are being accepted. Have you tried a different USB port? I know it sounds strange, but sometimes that can make a difference.
Click to expand...
Click to collapse
i did what tygerbyte suggested several times with no success. then i decided to reinstall htc drivers, restart the laptop, and use a different usb port like unremarked suggested, i am able to sideload now! flashing my backup i made in CWM right now, hopefully this will give me a working phone again before i try to flash a custom rom again lol.
i have my fingers crossed.
thanks for the suggestions everyone. ill post back in a bit with results.
just wanted to update, i was able to flash android revolution after several tries / freezing, but phone is back on and functional now.
thanks for walking me through this, i would have gone insane if i bricked my one.
mky4b11 said:
just wanted to update, i was able to flash android revolution after several tries / freezing, but phone is back on and functional now.
thanks for walking me through this, i would have gone insane if i bricked my one.
Click to expand...
Click to collapse
Isn't it the worst feeling, thinking you have bricked your $600 phone? I soft-bricked my husbands Bionic once, stayed up all night long and finally figured out I had skipped a step.
The BEST feeling, though, is realizing that you can, and did, recover from what appeared to be a catastrophic fail. Congratulations!
Ok guys...here it goes.
I've had a long night of feeling like the biggest idiot to walk the Android planet. I just bought this phone off someone, and have done rooting/custom ROM installing before. But I messed up, and now I feel like I'm an idiot & screwed because I'm just so lost now. I love learning, but I feel like I'm in such a hole. Here's what happened:
I used "All In One Kit" to install "TWRP 2.6.0.0", and like anybody, I wanted to install a custom ROM after getting all the rooting done. So I went searching for CW10.1, and tried to install it. Kept getting "Failed" every time I tried to install CW10.1 with "TWRP", so I started googling why. Well, it said I had to install the boot.img with the whole "fastboot" process where I use the command "fastboot flash boot boot.img". So I did that...and man was that a mistake.
My phone after, would just stay stuck at the boot screen. So I didn't panic, and I went into "TWRP" and tried to restore from the backup I did, before I started trying to install a custom ROM...but the same thing happened. Fast forward 2 hours and now I feel like I've screwed myself. I thought "TWRP" backed everything up, but for all I know, my moronic self might have unchecked "Boot". So I believe I need to "fastboot" the correct/original boot.img, so the phone will boot normally, but I have no idea where to find it. I've tried looking, but I'm more finding the issue is solved by using RUU. Which I REALLY don't mind doing at all, but I'm scared now since there are so many different ones, and I can't figure out which one is the right one to use. My night has taken such a crappy turn, I'm afraid if I RUU once wrong, I will be in an even bigger mess, than trying to reach out to you guys first. It's crazy how comfortable I was doing all this, and now I feel like I shouldn't have ever tried.
Here is the phone info I can provide that is hopefully helpful:
The phone is an HTC One X+ AT&T USA
EVITARE_UL PVT SHIP S-ON RL
HBOOT: 1.40.0000
CPLD-None
MICROP-None
RADIO-SSD: 2.14.55.01
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM TYPE: MDM9215M
Dec 28 2012, 22:18:14
And I believe it was at 4.2.1 software...but I'm not 100% on that and don't know how to make sure.
Please guys, if anybody can help, I need it. I appreciate your time in reading this, even if you cannot help. I believe I either just need a stock boot.img for my phone, or linked the correct RUU (assuming I'm right in that will fix it and revert me back to having a phone again). Any questions feel free to ask me. I'm going to try to sleep now.
krayzed896 said:
Ok guys...here it goes.
I've had a long night of feeling like the biggest idiot to walk the Android planet. I just bought this phone off someone, and have done rooting/custom ROM installing before. But I messed up, and now I feel like I'm an idiot & screwed because I'm just so lost now. I love learning, but I feel like I'm in such a hole. Here's what happened:
I used "All In One Kit" to install "TWRP 2.6.0.0", and like anybody, I wanted to install a custom ROM after getting all the rooting done. So I went searching for CW10.1, and tried to install it. Kept getting "Failed" every time I tried to install CW10.1 with "TWRP", so I started googling why. Well, it said I had to install the boot.img with the whole "fastboot" process where I use the command "fastboot flash boot boot.img". So I did that...and man was that a mistake.
My phone after, would just stay stuck at the boot screen. So I didn't panic, and I went into "TWRP" and tried to restore from the backup I did, before I started trying to install a custom ROM...but the same thing happened. Fast forward 2 hours and now I feel like I've screwed myself. I thought "TWRP" backed everything up, but for all I know, my moronic self might have unchecked "Boot". So I believe I need to "fastboot" the correct/original boot.img, so the phone will boot normally, but I have no idea where to find it. I've tried looking, but I'm more finding the issue is solved by using RUU. Which I REALLY don't mind doing at all, but I'm scared now since there are so many different ones, and I can't figure out which one is the right one to use. My night has taken such a crappy turn, I'm afraid if I RUU once wrong, I will be in an even bigger mess, than trying to reach out to you guys first. It's crazy how comfortable I was doing all this, and now I feel like I shouldn't have ever tried.
Here is the phone info I can provide that is hopefully helpful:
The phone is an HTC One X+ AT&T USA
EVITARE_UL PVT SHIP S-ON RL
HBOOT: 1.40.0000
CPLD-None
MICROP-None
RADIO-SSD: 2.14.55.01
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM TYPE: MDM9215M
Dec 28 2012, 22:18:14
And I believe it was at 4.2.1 software...but I'm not 100% on that and don't know how to make sure.
Please guys, if anybody can help, I need it. I appreciate your time in reading this, even if you cannot help. I believe I either just need a stock boot.img for my phone, or linked the correct RUU (assuming I'm right in that will fix it and revert me back to having a phone again). Any questions feel free to ask me. I'm going to try to sleep now.
Click to expand...
Click to collapse
i think installing an international ROM on an AT&T device was the downfall here
you need to install a ROM here for an example, by following the instructions given:
http://forum.xda-developers.com/showthread.php?t=2098218
leefear said:
i think installing an international ROM on an AT&T device was the downfall here
you need to install a ROM here for an example, by following the instructions given:
http://forum.xda-developers.com/showthread.php?t=2098218
Click to expand...
Click to collapse
No you are completely right. This is where I messed up, and everything went bad. My only problem is I'm not sure how to get the ROM on my device. Every time I try "ADB Sideload", it says it's starting...and then...that's it. I can cancel it, but it never actually goes through with the side load. What should I try to do in this case, so I can get the ROM loaded?
And thank you for your quick response, it's greatly appreciated!
krayzed896 said:
No you are completely right. This is where I messed up, and everything went bad. My only problem is I'm not sure how to get the ROM on my device. Every time I try "ADB Sideload", it says it's starting...and then...that's it. I can cancel it, but it never actually goes through with the side load. What should I try to do in this case, so I can get the ROM loaded?
And thank you for your quick response, it's greatly appreciated!
Click to expand...
Click to collapse
assuming you have the htc driver installed for your device, adb commands should work, can you test with adb devices that should list your phone, if not get your htc drivers installed and make sure you have latest adb on your pc
move NAMEOFROM.zip to adb folder and use the sideload option in twrp and sideload rom and should work
and don't forget to flash the boot.img provided
question rolermi
leefear said:
assuming you have the htc driver installed for your device, adb commands should work, can you test with adb devices that should list your phone, if not get your htc drivers installed and make sure you have latest adb on your pc
move NAMEOFROM.zip to adb folder and use the sideload option in twrp and sideload rom and should work
and don't forget to flash the boot.img provided
Click to expand...
Click to collapse
I definitely have the drivers installed, mostly because they were required as part of rooting with "All in One" tool. I never installed anything for ADB, I simply assumed it was just used as an option in "TWRP", so I'll go download that. Thank you, and I will update with my results!
Ok, posting an update!
Thank you for your response, as this fixed my problem! I will sum up my problem/fix in this reply, in case anybody is also trying to fix the same problem.
I have at HTC One X+ for AT&T
I was in a boot loop, after I had successfully rooted my phone with TWRP. I used "fastboot" method to change the boot.img, and lost my original in the process. Stuck only being able to boot to the system, or recovery, I needed a way to fix my boot problem. The suggested method worked flawlessy. I downloaded Android SDK, installed Platoform-Tools from the SDK Manager. Opened up ADB in ADT>SDK>Platform-Tools and followed the necessary steps for "pushing a ROM with ADB" I had found. I used the recommend link above for ViperXL+. I was able to push the ROM in, boot into recovery, and finally install a proper ROM. I then did the "fastboot" method to install the ROM ViperXL+'s boot.img (As a side note your .zip might show up as "sideload" and not the ROM title for the .zip I didn't know this, and thought it somehow lied to me is 100% completion, until I tried selecting "sideload" to install, which I didn't believe to have seen before. And sure enough it was the ROM)
Now my phone boots sucessfully, and I have a custom ROM. THANK YOU so much for your help, big kudos to leefear for explaining what I needed to do, and linking me the ROM. I appreciate it so much man!!!
krayzed896 said:
Ok, posting an update!
Thank you for your response, as this fixed my problem! I will sum up my problem/fix in this reply, in case anybody is also trying to fix the same problem.
I have at HTC One X+ for AT&T
I was in a boot loop, after I had successfully rooted my phone with TWRP. I used "fastboot" method to change the boot.img, and lost my original in the process. Stuck only being able to boot to the system, or recovery, I needed a way to fix my boot problem. The suggested method worked flawlessy. I downloaded Android SDK, installed Platoform-Tools from the SDK Manager. Opened up ADB in ADT>SDK>Platform-Tools and followed the necessary steps for "pushing a ROM with ADB" I had found. I used the recommend link above for ViperXL+. I was able to push the ROM in, boot into recovery, and finally install a proper ROM. I then did the "fastboot" method to install the ROM ViperXL+'s boot.img (As a side note your .zip might show up as "sideload" and not the ROM title for the .zip I didn't know this, and thought it somehow lied to me is 100% completion, until I tried selecting "sideload" to install, which I didn't believe to have seen before. And sure enough it was the ROM)
Now my phone boots sucessfully, and I have a custom ROM. THANK YOU so much for your help, big kudos to leefear for explaining what I needed to do, and linking me the ROM. I appreciate it so much man!!!
Click to expand...
Click to collapse
hey buddy, glad you got it working, nothing worse than a broken phone! glad i could help! now, hit that thanks button!
ooh, my 200th post!
leefear said:
hey buddy, glad you got it working, nothing worse than a broken phone! glad i could help! now, hit that thanks button!
ooh, my 200th post!
Click to expand...
Click to collapse
Congrats on the 200th post! Sorry, very new to using the forums. I hit thanks on all your posts in the topic! :good:
Hi,
i have the same problem but it's a non LTE version HOX+ can someone advise on another ROM that will work in the same way?
I'm stupid, I get it.
I just got an Asurion replacement DNA the other day and I wanted to S-Off, Root, Recovery Image, and new KitKat ROM.
So, I was able to use Rumrunner, and that worked out fine.
I rooted my DNA and then loaded TWRP 2.6.3, and that worked fine as well.
My intent was to load GPE and I d/l'd it to my phone (not knowing it was a corrupt download).
So I got into recovery, wiped, wiped, reset, and loaded the ROM - and it puked all over itself.
Now, I have a phone that is in recovery, has no image, and I can't figure out how to put one on it.
I'm running Mint Linux, but I have access to a W7 laptop if I need it.
It's my daily driver, I'm frustrated, upset, and stupid. And I could certainly use some help.
Thanks
In a terminal window (thanks .torrent), I typed: adb devices (then sudo adb devices) and got nothing in return.
I've tried sideloading; the ROM loads according to the terminal window, but I don't see anything happening on the phone (no failures though).
I've tried pushing a ROM to the phone but the terminal window says that it doesn't see the device. That doesn't make sense because I can sideload (apparently).
ugh.
Yehudah said:
In a terminal window (thanks .torrent), I typed: adb devices (then sudo adb devices) and got nothing in return.
I've tried sideloading; the ROM loads according to the terminal window, but I don't see anything happening on the phone (no failures though).
I've tried pushing a ROM to the phone but the terminal window says that it doesn't see the device. That doesn't make sense because I can sideload (apparently).
ugh.
Click to expand...
Click to collapse
This question has been answered at least a dozen times, "Help I wiped my internal storage", blah blah blah.
Download the rom you want on your computer. Put it in the same directory as your ADB stuff (mine is C:\android, I don't know what yours is).
Plug phone into computer, make sure you have ADB enabled on your phone, open a command prompt, verify you have ADB working by typing "adb devices"
You should see your device listed.
Boot phone into recovery >advanced >ADB sideload
Follow instructions at top of sideload screen to sideload rom from computer to phone.
In the future a little searching would get you to all this information, rather than starting a new thread... :good:
Enjoy
P.S. ALWAYS verify your MD5 before flashing, and ALWAYS have a backup made to fall back on.
I know it's been done to death. I searched and read every thread that was like mine and did everything in each thread.
It was the last thing I did that worked. RUU from .torrents links. That worked. I'm still rooted, Next time I'll make sure I have I backup I can restore - won't make this mistake again.
Thanks for the low level chastising, I deserved it. And thanks for the info, ad nauseum.
After a two day ordeal, I finally got my DNA back to where it was before I borked it up last week.
Because of what I did; I needed to use Rumrunner to unlock, RUU to get back to where the phone worked, ADB and Fastboot to get the recovery image set up and put a ROM on the phone.
When it was all said and done, .torrent walked me through getting the phone fixed. Without him, I'd still be banging my head against my desk.
Thanks to the developers who created Rumrunner, and who developed the Android tool kits that helped me overcome my stupidity. Because of their ability to create great applications, I've learned more about Linux and how my phone works than I ever did before....just wish it hadn't taken this to cause that.
Thanks to all, you guys ROCK! :good:
Yehudah said:
After a two day ordeal, I finally got my DNA back to where it was before I borked it up last week.
Because of what I did; I needed to use Rumrunner to unlock, RUU to get back to where the phone worked, ADB and Fastboot to get the recovery image set up and put a ROM on the phone.
When it was all said and done, .torrent walked me through getting the phone fixed. Without him, I'd still be banging my head against my desk.
Thanks to the developers who created Rumrunner, and who developed the Android tool kits that helped me overcome my stupidity. Because of their ability to create great applications, I've learned more about Linux and how my phone works than I ever did before....just wish it hadn't taken this to cause that.
Thanks to all, you guys ROCK! :good:
Click to expand...
Click to collapse
At least you learned from your mistakes.
Sent from my HTC6600LVW using XDA Premium 4 mobile app
thayl0 said:
At least you learned from your mistakes.
Sent from my HTC6600LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you using an HTC 6600 as your daily driver? LOL I had one of those, loved it.
Yehudah said:
Are you using an HTC 6600 as your daily driver? LOL I had one of those, loved it.
Click to expand...
Click to collapse
I'm not use haven't looked I'm using whatever it installed. lol
Hey folks,
First time poster here, but have been following this awesome community for a few months now. So with that being said, I've landed myself in deeper water then I had hoped to see on my first foray into the world of tinkering on my tablet. I feel I should also disclose my epic newb moment, where in I ran headlong off the cliff with making proper (any) backups
I've been doing a lot of reading the last couple days to try and solve the issue, found lots of radical advice, but sadly haven't managed to get myself any further ahead. I was hoping that with a little list of what the TF201 is doing & what I've tried since, that you folks might be able to shed some light on what I've done and what I can try.
The Problem:
I've got a TF201, unlocked, TWRP 2.6.3.0. ADB access from command prompt. Sadly that's all I've got at this time (No OS, No fastboot). I cannot seem to install an OS now, but can still push files over to the tablet/view them. As far as I can tell, I'm have Brick 1a from this post: http://forum.xda-developers.com/showthread.php?t=1514088 . It references (CWM), so Im not sure these steps are applicable (My understanding is this is a recovery manager though I could be mistaken).
I've also explored:
[TOOL][WINDOWS-ONLY]WSG UnBricker V1.0.2
http://forum.xda-developers.com/showthread.php?t=1599991
But don't have fastboot access.
Unrecoverable bootloader error but not Bricked!
http://forum.xda-developers.com/showthread.php?t=2179759
But don't have fastboot access.
[ROOT] Urkel's Fresh Start 1.0 (Jelly Bean - Unlocked bootloaders only)
http://forum.xda-developers.com/showthread.php?t=1929189
Again appears to need fastboot access.
Etc.
So my question is, is there a process I can follow from TWRP to get me back to fastboot access? OR am I looking at the problem from the wrong angle? Any advice or suggestions would be appreciated. Apoligies in advance if this is addressed elsewhere! If there is any additional info I can provide please let me know.
***Update***
Now have fastboot access, continuing to proceed with caution. Attempting to install a rom now.
***Update 2***
Still have fastboot access, however now can't access recovery when I fastboot devices my device now shows up as ??????????? Fastboot, rather then the letters/numbers it used to show. Feeling like I've slid her a little deeper into the mud. Also a lot of "unrecoverable boot error 0x00000000"
***Update 3***
http://forum.xda-developers.com/showthread.php?t=2179759&page=2 Progress
Light_Canuck said:
Hey folks,
First time poster here, but have been following this awesome community for a few months now. So with that being said, I've landed myself in deeper water then I had hoped to see on my first foray into the world of tinkering on my tablet. I feel I should also disclose my epic newb moment, where in I ran headlong off the cliff with making proper (any) backups
I've been doing a lot of reading the last couple days to try and solve the issue, found lots of radical advice, but sadly haven't managed to get myself any further ahead. I was hoping that with a little list of what the TF201 is doing & what I've tried since, that you folks might be able to shed some light on what I've done and what I can try.
The Problem:
I've got a TF201, unlocked, TWRP 2.6.3.0. ADB access from command prompt. Sadly that's all I've got at this time (No OS, No fastboot). I cannot seem to install an OS now, but can still push files over to the tablet/view them. As far as I can tell, I'm have Brick 1a from this post: http://forum.xda-developers.com/showthread.php?t=1514088 . It references (CWM), so Im not sure these steps are applicable (My understanding is this is a recovery manager though I could be mistaken).
I've also explored:
[TOOL][WINDOWS-ONLY]WSG UnBricker V1.0.2
http://forum.xda-developers.com/showthread.php?t=1599991
But don't have fastboot access.
Unrecoverable bootloader error but not Bricked!
http://forum.xda-developers.com/showthread.php?t=2179759
But don't have fastboot access.
[ROOT] Urkel's Fresh Start 1.0 (Jelly Bean - Unlocked bootloaders only)
http://forum.xda-developers.com/showthread.php?t=1929189
Again appears to need fastboot access.
Etc.
So my question is, is there a process I can follow from TWRP to get me back to fastboot access? OR am I looking at the problem from the wrong angle? Any advice or suggestions would be appreciated. Apoligies in advance if this is addressed elsewhere! If there is any additional info I can provide please let me know.
***Update***
Now have fastboot access, continuing to proceed with caution. Attempting to install a rom now.
***Update 2***
Still have fastboot access, however now can't access recovery when I fastboot devices my device now shows up as ??????????? Fastboot, rather then the letters/numbers it used to show. Feeling like I've slid her a little deeper into the mud. Also a lot of "unrecoverable boot error 0x00000000"
Click to expand...
Click to collapse
Get yourself back into fastboot. I'm guessing you got there by typing adb reboot fastboot from in TWRP.
You will need to make sure your fastboot and adb exes are compatible so try these. http://flumpster.lolcakes.com/android/adb-fastboot.zip
I know they are old but I also know they worked.
Next you would have to make sure you had the correct drivers installed. I've always used these. http://www.koushikdutta.com/post/universal-adb-driver
Now follow the instructions here http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
But where he says to get the TF300 firmware etc get the TF201 instead.
EDIT : Are you also sure you are in fastboot and not in APX mode. Explain how you got to fastboot please.
Thanks for the reply flumpster, I was actually working my way through that when you posted. So now I can get into fastboot, however I have no OS installed currently. I'll keep poking at it, I feel progress is being made
EDIT
I am powering down and holding volume down. I may have a terminology issue here, but that is what I believed was fastboot.
EDIT 2
Also confirmed adb and fastboot are working, and confirmed Im using the same driver you recomended. I am now sitting with 4 options, RCK, Android, USB & Wipe Data.
With much fandangling, have got myself back to a bootable environment running the rom located here: http://forum.xda-developers.com/showthread.php?t=2147895
From what I gather I should get my backups made asap, NVflash seems to be the most commonly mentioned, but am getting an error with step 1 in wheelies. However, its another issue so I shall consider this thread case closed and go back to reading. Thanks again for the help!
So i just decided to join the rest of the world and get myself a rectangle. so i researched the 1 to 200 dollar range for weeks until i found my new shiny metal friend with great specs and a price that wouldn't keep me up at night. the le max 2 x829. but i love tech and was really looking forward to pushing this phone and learn about all it could do! i was really excited.
Until i started to learn about the many confusing programs needed to install custom roms or make a recovery file. things like that All of which need like 6 different programs all of which seem to need some other program in order to functional. I can't seem to even find a starting point! I HAVE NEVER FELT THIS STUPID IN MY ENTIRE LIFE. Someone please help. what programs do i need for a new os ? How does adb fit into the chain of programs needed to mod android? is twrp the first program needed? how does it all sort...fit to gather? Thanks for any help!
Man, honestly this forum is made to help people, but also people should use the search button. This question has been answered a million times already.
Long story short:
- Connect the phone to the PC and install the drivers (including ADB)
- Unlock bootloader (usually it's already unlocked)
- Download TWRP on your PC
- Install TWRP following the developer's steps
- Download your custom ROM
- Put the ROM on the internal memory
- Boot into TWRP
- Install the new ROM according to the instructions given by the developer and you're done...
valy_cta said:
Man, honestly this forum is made to help people, but also people should use the search button. This question has been answered a million times already.
Long story short:
- Connect the phone to the PC and install the drivers (including ADB)
- Unlock bootloader (usually it's already unlocked)
- Download TWRP on your PC
- Install TWRP following the developer's steps
- Download your custom ROM
- Put the ROM on the internal memory
- Boot into TWRP
- Install the new ROM according to the instructions given by the developer and you're done...
Click to expand...
Click to collapse
including adb? what other drivers do i need? xposed? supersu? ...i have done my research by the way...its just not making alot of sense..thats all. i know all you old pros have probably been at it for years but i never even held a smartphone until 6 days ago ha ha
valy_cta said:
Man, honestly this forum is made to help people, but also people should use the search button. This question has been answered a million times already.
Long story short:
- Connect the phone to the PC and install the drivers (including ADB)
- Unlock bootloader (usually it's already unlocked)
- Download TWRP on your PC
- Install TWRP following the developer's steps
- Download your custom ROM
- Put the ROM on the internal memory
- Boot into TWRP
- Install the new ROM according to the instructions given by the developer and you're done...
Click to expand...
Click to collapse
Also how do you download twrp on you're pc ? it won't let me i have it on my phone but it just keeps leading me to a website to download again.
Serialjwalker said:
Also how do you download twrp on you're pc ? it won't let me i have it on my phone but it just keeps leading me to a website to download again.
Click to expand...
Click to collapse
Do you have it installed on the phone or just downloaded? If it's installed, jump over that step. If it's just downloaded, connect the phone to the pc by cable, transfer the files :cyclops:
I understand your concern. It's because there are a few ways of doing it, and so novices might be confused when comparing two different tutorials.
This one is very complete: https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
1. Connect your phone, it is supposed to install drivers automatically.
1.1 If not, you'll need to google it, but I believe this toolkit will help you. In fact, this tool is capable of doing all the process for you by simply clicking on some buttons.2. Install ADB Drivers. There are a few options and it is basically
2.1 @greenManGaming recommends 15 seconds ADB installer.
2.2 (Alternative) Minimal ADB and Fastboot. I've used this one.
2.3 (Alternative) ADB and Fastboot (newer) or Universal ADB and Fastboot (older) from the same dev.
OBS: I'm not sure if the toolkit requires or not one of these options to work properly or if it already does this task.3. Download TWRP (on your computer).
3.1 Follow the instructions from the official page. In short, put the img into the ADB folder.4. Follow the commands in the the tutorial mentioned.
4.1 In short, unlock the bootloader, boot twrp, complete backup, reboot into the system, copy the backup to your PC/Cloud service, get back to fastboot mode, flash twrp, then flash your ROM.
OBS: Suggestion for only booting TWRP at the first time is perfectly optional, you can flash it since the beginning but in this case you wouldn't be able to backup the original recovery and everything as the phone came, in case you need go back to request an RMA.
razmth said:
I understand your concern. It's because there are a few ways of doing it, and so novices might be confused when comparing two different tutorials.
This one is very complete: https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
1. Connect your phone, it is supposed to install drivers automatically.
1.1 If not, you'll need to google it, but I believe this toolkit will help you. In fact, this tool is capable of doing all the process for you by simply clicking on some buttons.2. Install ADB Drivers. There are a few options and it is basically
2.1 @greenManGaming recommends 15 seconds ADB installer.
2.2 (Alternative) Minimal ADB and Fastboot. I've used this one.
2.3 (Alternative) ADB and Fastboot (newer) or Universal ADB and Fastboot (older) from the same dev.
OBS: I'm not sure if the toolkit requires or not one of these options to work properly or if it already does this task.3. Download TWRP (on your computer).
3.1 Follow the instructions from the official page. In short, put the img into the ADB folder.4. Follow the commands in the the tutorial mentioned.
4.1 In short, unlock the bootloader, boot twrp, complete backup, reboot into the system, copy the backup to your PC/Cloud service, get back to fastboot mode, flash twrp, then flash your ROM.
OBS: Suggestion for only booting TWRP at the first time is perfectly optional, you can flash it since the beginning but in this case you wouldn't be able to backup the original recovery and everything as the phone came, in case you need go back to request an RMA.
Click to expand...
Click to collapse
more questions....twrp will only load onto my phone and not my pc? also there are no adb driver folders just an exe. what do i do about that?
someone tell me how to delete this thread...i am just going to sell my smartphone i can't look at it anymore. every thing i try to do with it it resists every single inch of the way. nothing works according to instructions. i thought this would be fun but its hell... i give up! ...it wins going to trade this thing for the first 30 dollar burner phone i can find
Huge drama for nothing. Sell the thing, it's obviously not for you. If you can't follow some simple instructions, then it's better to sell it to some guy who likes to try at least.
valy_cta said:
Huge drama for nothing. Sell the thing, it's obviously not for you. If you can't follow some simple instructions, then it's better to sell it to some guy who likes to try at least.
Click to expand...
Click to collapse
maybe they are laid out to be simple but nothing is working as instructed. i have been at it for a week . so far installing firefox is the best i can seem to do lol simple? theres nothing simple about the gangbang of programs you need to do stuff on these phones. none of which can actually be compelled to function under any circumstances at least for me.
Serialjwalker said:
maybe they are laid out to be simple but nothing is working as instructed. i have been at it for a week . so far installing firefox is the best i can seem to do lol simple? theres nothing simple about the gangbang of programs you need to do stuff on these phones. none of which can actually be compelled to function under any circumstances at least for me.
Click to expand...
Click to collapse
If you are not familiar with giving commands with command prompt, installing drivers and needed software (android studio or minimal adb install) then you are in for a challenge, if you are not willing to learn its better to sell the phone or use it with de preinstalled android.
i find myself quite skilled( have flashed several brands of phoned in the last 5 years) and it took me a couple of days to figure out what to do and how to install twrp and my first rom, there are no one click shortcuts for this phone
Why need to install rom? It already work.
Serialjwalker said:
more questions....twrp will only load onto my phone and not my pc? also there are no adb driver folders just an exe. what do i do about that?
Click to expand...
Click to collapse
Did you try watching different videos to have a big picture of the process? It would be the first step. Even if you don't understand English, simply watch it. You'll see what would happen after each action.
Then check the written tutorial. Not a big issue at all. Really. Even for newbies, I've been one when I had a Galaxy 5, my first android that doesn't even needed to flash a custom ROM.
Whether you think you can, whether you think you can't, you're right.
The command to load the TWRP will be done on your PC, however, only your phone will load it. In short, you'll be commanding your phone through your PC.
When you install Minimal ADB and Fastboot, it will install its files in a default folder. Inside its default folder is where you should place the TWRP image.
Sent from my Le X820 using Tapatalk