Ok so I just got the One M7 and I hate Sense, like really hate it so I went on to install CM11 via CyanogenMod Installer (Like MKBHD did, that's why I thought I should) and I did everything it said, Opened up the app on my phone followed the instructions until it said "Continue installation on your computer" and I did, when I opened the CM Installer however, it never detects my phone! I don't have HTC Drivers nor HTC Sync manager, but I heard that it isn't needed, help
CesarRaimon said:
Ok so I just got the One M7 and I hate Sense, like really hate it so I went on to install CM11 via CyanogenMod Installer (Like MKBHD did, that's why I thought I should) and I did everything it said, Opened up the app on my phone followed the instructions until it said "Continue installation on your computer" and I did, when I opened the CM Installer however, it never detects my phone! I don't have HTC Drivers nor HTC Sync manager, but I heard that it isn't needed, help
Click to expand...
Click to collapse
if your phone must communicate with your pc at some point, you must have the drivers installed even if its not specified
Btw this is very simple to flash CM using a custom recovery if the installer doesn't work.
install the drivers using this guide:
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
-------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
alray said:
if your phone must communicate with your pc at some point, you must have the drivers installed even if its not specified
Btw this is very simple to flash CM using a custom recovery if the installer doesn't work.
install the drivers using this guide:
Click to expand...
Click to collapse
woah thanks for the quick response, I'll try that and report shortly, thanks again
CesarRaimon said:
woah thanks for the quick response, I'll try that and report shortly, thanks again
Click to expand...
Click to collapse
The problem using the CM installer is that you don't have any option to revert back to stock which is possible when you flash the rom from recovery. (you can make a nandroid backup before flashing the rom)
So if you need to send your phone to repair under warranty, can you return to stock? Is there a ruu for your phone if you don't have a backup?
alray said:
The problem using the CM installer is that you don't have any option to revert back to stock which is possible when you flash the rom from recovery. (you can make a nandroid backup before flashing the rom)
So if you need to send your phone to repair under warranty, can you return to stock? Is there a ruu for your phone if you don't have a backup?
Click to expand...
Click to collapse
I'm really not willing to go back to stock, and the warranty is already expired so I got nothing to lose really, don't know what RUU is
CesarRaimon said:
I'm really not willing to go back to stock, and the warranty is already expired so I got nothing to lose really, don't know what RUU is
Click to expand...
Click to collapse
ok its up to you :angel:
btw I like this name.... Raymond
alray said:
ok its up to you :angel:
btw I like this name.... Raymond
Click to expand...
Click to collapse
Thanks! Like the name Alray!
And what's RUU btw, any links would be much appreciated
CesarRaimon said:
Thanks! Like the name Alray!
And what's RUU btw, any links would be much appreciated
Click to expand...
Click to collapse
RUU is for Rom Update Utility. Its the most common way to restore HTC devices back to stock from your computer. It can also be used to updated a phone if something is messed up and prevent the ota update to install. It flashes/update stock hboot, stock recovery, stock radio, stock software (rom).... stock everything.... But to use a ruu you must find one that is specifically for your phone model, software, CID and MID.
RUU for the htc one M7 can be found here http://www.htc1guru.com/
alray said:
RUU is for Rom Update Utility. Its the most common way to restore HTC devices back to stock from your computer. It can also be used to updated a phone if something is messed up and prevent the ota update to install. It flashes/update stock hboot, stock recovery, stock radio, stock software (rom).... stock everything.... But to use a ruu you must find one that is specifically for your phone model, software, CID and MID.
RUU for the htc one M7 can be found here http://www.htc1guru.com/
''ray'' in alray is for Raymond thats why I like it...
Click to expand...
Click to collapse
Aha so it's kinda like Odin for Samsung devices! and I see what you did there
Related
this is compiled form pure ClockWorkMod sources.
and i do a little modified.
now it's using the htc stock processbar and background.
use at you own risk.
i've already tested it, all function works as it should.
Please unlock your bootloader via htcdev.com
then use fastboot to flash this.
Code:
fastboot flash recovery recovery.img
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads :
View attachment runnymede-cwm-recovery.zip
Has anyone had a play with this yet? Im reluctant due to no official word from Koush yet...
very nice work, now we just need someone to try flash the rom hehe
it works so why do we need koush for everything...... there are others who are just as capable. this along with chinese version work so i am happy. now try cappy rom lol
---------- Post added at 03:37 PM ---------- Previous post was at 03:19 PM ----------
flashed this recovery.img which is english and it works. just backing up my original rom now to flash cappys runnymede v1.1. excited as well. back up completed without a hitch and mounted usb storage in recovery. all seems fine guys for now
---------- Post added at 03:56 PM ---------- Previous post was at 03:37 PM ----------
did wipe data/factory reset which completed successfully and install zip from sdcard etc so i am happy with it for now
shingers5 said:
it works so why do we need koush for everything...... there are others who are just as capable. this along with chinese version work so i am happy. now try cappy rom lol
---------- Post added at 03:37 PM ---------- Previous post was at 03:19 PM ----------
flashed this recovery.img which is english and it works. just backing up my original rom now to flash cappys runnymede v1.1. excited as well. back up completed without a hitch and mounted usb storage in recovery. all seems fine guys for now
---------- Post added at 03:56 PM ---------- Previous post was at 03:37 PM ----------
did wipe data/factory reset which completed successfully and install zip from sdcard etc so i am happy with it for now
Click to expand...
Click to collapse
this is based on Koush's Open Sources ClockWorkMod Recovery, so indeed we need Koush. we should thank koush for his great work and contribution for this community. BTW. Thanks for confirming this is working.
tenfar said:
this is based on Koush's Open Sources ClockWorkMod Recovery, so indeed we need Koush. we should thank koush for his great work and contribution for this community. BTW. Thanks for confirming this is working.
Click to expand...
Click to collapse
nope i dint mean it like that mate. yea all of this wouldnt be possible without him but we shouldnt be reluctant to try it just cause he hasnt endorsed it. just cause you posted it dont mean it wont work ..................... as i can testify it works and quite well. i just done a full restore from back up and it went through flawlessly. thanks again to you and koush for his open sopurces.
shingers5 said:
nope i dint mean it like that mate. yea all of this wouldnt be possible without him but we shouldnt be reluctant to try it just cause he hasnt endorsed it. just cause you posted it dont mean it wont work ..................... as i can testify it works and quite well. i just done a full restore from back up and it went through flawlessly. thanks again to you and koush for his open sopurces.
Click to expand...
Click to collapse
Can i ask how you got S-OFF? On the HTCdev.com it doesn't have sensation XL listed
wwfc said:
Can i ask how you got S-OFF? On the HTCdev.com it doesn't have sensation XL listed
Click to expand...
Click to collapse
its there. i take it you mean unlock bootloader? s-off isnt available as yet from what i can see but from htc dev you can unlock ya bootloader. HTC sensation xl or runnymede(RUNNYMEDE) - same phone
shingers5 said:
its there. i take it you mean unlock bootloader? s-off isnt available as yet from what i can see but from htc dev you can unlock ya bootloader. HTC sensation xl or runnymede(RUNNYMEDE) - same phone
Click to expand...
Click to collapse
Hi all, on the htc dev website i cant see the sensation xl at all..... are you using the sensation xe htc sync?
+1,
Same.....no Sensation xl or runnymede found
Can someone write a Howto?
Or somebody have it uploadet to a mirror?
I think, there are some progs for download, to manage the unlock....
I have Rom 207, normally 407, so I wonder, if it is O2-Germany brandet....
Can I unlock my Bootloader too?
jammysunny said:
+1,
Same.....no Sensation xl or runnymede found
Can someone write a Howto?
Or somebody have it uploadet to a mirror?
I think, there are some progs for download, to manage the unlock....
I have Rom 207, normally 407, so I wonder, if it is O2-Germany brandet....
Can I unlock my Bootloader too?
Click to expand...
Click to collapse
you dont need to see it in the list. it did not show in the list does not mean it can not been unlocked. just follow the steps. you can unlock your phones bootloader if you can use fastboot command to get the identify token.
I have 207 in Softwareinfo, so, can I do it with this O2-Rom too?
Damn, I cant install JDK.....any help??
jammysunny said:
Damn, I cant install JDK.....any help??
Click to expand...
Click to collapse
can somebody upload a original recovery image file so can be flashed back?
---------- Post added at 08:28 AM ---------- Previous post was at 08:19 AM ----------
jammysunny said:
Damn, I cant install JDK.....any help??
Click to expand...
Click to collapse
first write down whats your problem?
Ok, sorry,
I wanted to unlock the bootloader, so I registered me on the page "htcdev.com", to do it....
But before unlocking, I wanted to check my Java and my SDK, so I installed my Java, but it couldnt be installed
And thats the base of the SDK, so my first step doesnt be positive....
Edit: I managed it, cool!!
I had a problem with my defy (I replaced a system file), and now it doesn't start into androdi, so I need to flash a custom recovery with RSD Lite.
..but I can't find an image file with only CWM.
Could you please share how did you recompile CWM?
Thanks in advance!
how to flash it in fastboot ?
Vry.I.Prsn said:
how to flash it in fastboot ?
Click to expand...
Click to collapse
Firstly I would suggest using the Paul O'Brein recovery from the MoDaCo site
http://android.modaco.com/topic/348973-clockworkmod-recovery-5027-unofficial-modaco-edition/
Also have you got the Fastboot tools on your computer, you will need these to be able to install CWM and they're part of the android sdk package. Once you have the fastboot tools, move the recovery.img to the folder where fastboot.exe is and open a command window (I take it your using windows... hold left shift button and then right click, in the options you will see 'open command prompt here') and from the command prompt type this
fastboot flash recovery r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img (tip is to type r1 then hit tab to complete full line without typing it all)
This has all been explained in other threads...
I was bored today at work, so I've download and flashed this Recovery
My process was;
Stock
November time I unlocked the Bootloader
waited mainly due to lazyness
Today downloaded this Recovery
Flashed recovery via fastboot
Jobs a good 'un
Done a backup and waiting on RCMix3D Runny to download then install etc
No special tools or tricks of the trade, have had the SDK etc installed on my PC here since my G1 on launch day,, well soon after launch day anyway
[vertigo] said:
Firstly I would suggest using the Paul O'Brein recovery from the MoDaCo site
http://android.modaco.com/topic/348973-clockworkmod-recovery-5027-unofficial-modaco-edition/
Also have you got the Fastboot tools on your computer, you will need these to be able to install CWM and they're part of the android sdk package. Once you have the fastboot tools, move the recovery.img to the folder where fastboot.exe is and open a command window (I take it your using windows... hold left shift button and then right click, in the options you will see 'open command prompt here') and from the command prompt type this
fastboot flash recovery r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img (tip is to type r1 then hit tab to complete full line without typing it all)
This has all been explained in other threads...
Click to expand...
Click to collapse
I just keep getting <waiting for device>
Hey all
As the title says my Xperia z micro usb door is damaged so i cant charge or plug the mobile through my pc to restore the original firmware and send it back for reparation.
Is there any way to restore the firmware by using the micro sd?
Actually im charging the mobile using the dock. But since i dont like the battery life of the mobile..im thinking to fix it and sell it and buy new mobile.
Thanks for help
wiimourad said:
Hey all
As the title says my Xperia z micro usb door is damaged so i cant charge or plug the mobile through my pc to restore the original firmware and send it back for reparation.
Is there any way to restore the firmware by using the micro sd?
Actually im charging the mobile using the dock. But since i dont like the battery life of the mobile..im thinking to fix it and sell it and buy new mobile.
Thanks for help
Click to expand...
Click to collapse
If your phone has recovery installed you might be able to flash a stock ROM zip to put it back to its original firmware, otherwise u would need to use flashtool and flash a firmware via usb for it to be restored
Mackay53 said:
If your phone has recovery installed you might be able to flash a stock ROM zip to put it back to its original firmware, otherwise u would need to use flashtool and flash a firmware via usb for it to be restored
Click to expand...
Click to collapse
i got a FTF file with 758mb
is it that one?
wiimourad said:
i got a FTF file with 758mb
is it that one?
Click to expand...
Click to collapse
You can only flash an FTF via flashtool via USB
Are you rooted and have a recovery installed?
Mackay53 said:
You can only flash an FTF via flashtool via USB
Are you rooted and have a recovery installed?
Click to expand...
Click to collapse
yes is rooted and i got cyanogenmod on it...so i guesse there is a recovery
wiimourad said:
yes is rooted and i got cyanogenmod on it...so i guesse there is a recovery
Click to expand...
Click to collapse
You should be able to put the zip file onto the SD card and flash it via recovery. I'm guessing u never backed up your original ROM when you first installed recovery?
If that doesnt work, you could also try moving it to your phone through google drive?
Sent from my Nexus 5 using xda app-developers app
Could he restore to completely stock using a backup of somebody else's XZ?
Or could that cause issues?
Mackay53 said:
You should be able to put the zip file onto the SD card and flash it via recovery. I'm guessing u never backed up your original ROM when you first installed recovery?
Click to expand...
Click to collapse
i didnt unfortunaly
So i just have to put the FTF into my Sd card and flash via recovery?
How exactly?! Can you please link the intire procedure
If that doesnt work, you could also try moving it to your phone through google drive?
Click to expand...
Click to collapse
The sd card work fine,but if you mean that i have to download the FTF to internal storage and restore it via recovery is not a problem.
You cannot flash FTF files in recovery. They are for use with Flashtool only.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kingvortex said:
You cannot flash FTF files in recovery. They are for use with Flashtool only.
Click to expand...
Click to collapse
Is there any other way to bring back the mobile to his original status?
Completely stock? I don't think so, unfortunately.
I don't think it should matter when returning the device for a hardware defect though. The rom you're running didn't break your USB port.
wiimourad said:
Is there any other way to bring back the mobile to his original status?
Click to expand...
Click to collapse
You can get close enough
Install NUT's pre-rooted (odex version) rom through recovery.
While in recovery do a wipe. /data/factory reset.
Then flash my XZDR removal tool http://d-h.st/wOc
Reboot and you will be back on pure stock with root.
Then just do a full unroot from within SuperSU app.
Done
Edit: Hopefully your bootloader is locked But as @kingvortex said - its got nothing to do with a broken port
Sent from my C6603 using xda app-developers app
Hmm, good thinking, but does [NUT]'s flashable zip include the kernel? I was under the (perhaps mistaken) impression that the stripped FTF had to be flashed with Flashtool for the kernel and baseband. If I'm correct, then the rom will not boot with the CM kernel (correct me if I'm wrong). In that case, DooMLoRD's advanced stock kernel is a possibility, but that is still not fully stock and would require that the bootloader remain unlocked.
There's also the fact that the OP is on a CM rom, so therefore fastboot is needed to relock the bootloader even if a fully stock system is achieved.
It all depends on how closely the service centre looks at the software on the phone, I suppose.
Oh OK. So he is on CM11? - missed that. I was hoping he was on stock based.
Yeah your probably right about the stock kernel being in the stripped FTF. (Never tried it), however there is still a way. A little convoluted though, and I don't have time for a new tutorial.
Easiest way is, as you said, just take the damn thing to the repair centre and argue that customizing the phone has nothing to do with a faulty USB port
Sent from my Full Android on C6603 using xda app-developers app
Yeah, he didn't say he was on CM until post #5. I'm used to people not being forthcoming with all pertinent information here, so read through his other posts before replying.
I think it's possible to package a stock kernel up in a flashable zip. If it is, it may be possible to get back to stock. I'll look for the post where I saw it.
Edit - Found it.
http://forum.xda-developers.com/showthread.php?t=2470280
So, maybe -
1. Flash [NUT]'s rom.
2. Flash stock kernel packaged by the method above.
3. Wipe /data.
4. Flash your XZDR removal tool.
5. Reboot.
That may work. Trouble is, performing steps like this without the safety net of Flashtool or even fastboot in the event of something going wrong is quite risky, so nobody blame me if a brick happens!
Even if all is successful, the bootloader will still be unlocked, so hopefully the service centre will not check.
kingvortex said:
Completely stock? I don't think so, unfortunately.
I don't think it should matter when returning the device for a hardware defect though. The rom you're running didn't break your USB port.
Click to expand...
Click to collapse
they might say the usb door is broken coz you use it to perform software modification
Are you sure about this info?
i bought the mobile from Amazon.de
wiimourad said:
they might say the usb door is broken coz you use it to perform software modification
Are you sure about this info?
i bought the mobile from Amazon.de
Click to expand...
Click to collapse
Well, no I'm not sure as I haven't had to take mine to service, but how would changing the software on the phone physically break it?
kingvortex said:
Well, no I'm not sure as I haven't had to take mine to service, but how would changing the software on the phone physically break it?
Click to expand...
Click to collapse
an intense usage of the door would break it..or a high voltage caused by the software modification...you know how they think.
is it possible to have the link for
1:[NUT]'s rom
2:XZDR removal tool
thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[Hey Folks ! M Writing this so that everyone can easily root their Android One (Lollipop)
Pre-Request-A Custom Recovery Should be pre-installed on Device
STEPS -
1- Download The zip provided here !
2-Flash it Using TWRP/CWM (Any Recovery)
3-It will install automatically (No need to be Geeky here):cyclops:
4-Reboot The Phone
5-Open SU
6-It will give you a message "Need to upgrade database" or something like it
7- Install it .
8-Select Custom Mode
9-Reboot
10- Yeah your Phone is rooted now !
NOTE-Sorry if u encounter any problems !
Let me know my mistakes which are in the post and do comment if it works
Thank You !~:laugh:
EXTREME NEWBIE VERSION !!!!
BTW they have to use their PC to unlock Bootloader and flash custom recovery! :3
Thanks for being n00b friendly
Shreeshu10 said:
BTW they have to use their PC to unlock Bootloader and flash custom recovery! :3
Thanks for being n00b friendly
Click to expand...
Click to collapse
how to flash recovery?
Rmyaseen said:
how to flash recovery?
Click to expand...
Click to collapse
Search android one thread !
uh
If i flash recovery again, will i lost my data/OS or something? I installed Lollipop on my Xperia S about a week ago and i can't get to recovery mode to install .zip files, which is strange. I dont want to install etc. everything again so please, let me know how to deal with this. Also i turned off the "ambient thing", but its still pretty sensitive - it keeps unlocking itself when I put in on my bike or just when im trying to clean it which never happened to me before.
dasdsa
Pleaseeeeeeeeee! I really need it.
What zip file to download ?
I cannot root my Micromax xpress 2 e313 running on 5.1,this method fails in my mobile,please suggest any other method
I cant root my Intex Aque Power HD.. it has Lolipop 5.1 ..
I try to root with iroot apps, USB debug with my Lapy..
Hahahaha! Yeah right...let me see you install CWM or TWRP without a PC.
Same here
Hey! I also doing same bt my Micromax e313 also not root
noMercy1337 said:
If i flash recovery again, will i lost my data/OS or something? I installed Lollipop on my Xperia S about a week ago and i can't get to recovery mode to install .zip files, which is strange. I dont want to install etc. everything again so please, let me know how to deal with this. Also i turned off the "ambient thing", but its still pretty sensitive - it keeps unlocking itself when I put in on my bike or just when im trying to clean it which never happened to me before.
Click to expand...
Click to collapse
You cannot lose your data or OS by flashing a recovery. However if you do it incorrectly or use the wrong process to flash the recovery, you can brick your phone. And if you bricked it, you may have to flash a new stock ROM to unbrick. That may cause you to lose your data.
So as always, BACK UP YOUR OS AND YOUR DATA before you mess with your phone! I can't tell you how many people I read about who fail to backup their phone and then they mess with it not really knowing what they are doing and end up losing everything because they've bricked their phone and have NO BACKUP!
Don't risk your data. Back it up NOW. Then you can mess with your phone freely and without worry.
Sent from my Nexus 7 using XDA Free mobile app
How can i root cherry mobile flare s3 power lollipop
dangaw said:
How can i root cherry mobile flare s3 power lollipop
Click to expand...
Click to collapse
Yo, just use latest kingroot beta version, it may works
Recovery for our device is not available . Can you help ? I give you the Stock recovery image . Port one for me.
http://www.indishare.co/stdb32knjrk1
Thanks!!!
Sharique244777 said:
Pre-Request-A Custom Recovery Should be pre-installed on Device
Click to expand...
Click to collapse
No device comes with a pre-installed Custom Recovery! to install a Custom Recovery, you will need a PC.
Shreesha.Murthy said:
BTW they have to use their PC to unlock Bootloader and flash custom recovery! :3
Thanks for being n00b friendly
Click to expand...
Click to collapse
Where's the. Zip file download link?
An app that tends to work on almost all lollipop based devices is the KINGROOT app........
Just google it and download it....
Your phone may reboot during the root process but thanks to lollipop's ram feature your unclosed apps stay unclosed nd in the memory even after rebooting......
so carry on with the process after reboot(if it occurs)
I've rooted many stubborn devices with it
Hi so I've spent a good deal of the morning attempting to finally fix this phone, a couple years ago I removed all OS from it and no backup but I still have TWRP.
The phone is tampered/unlocked.
Hboot is 1.54.0000
I tried loading one of the latest ROMS from here via side loading - http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
I used this guide - http://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/
Unfortunately once the sideload is complete I get an error E: Zio file is corrupt, I was wondering if anyone knows what I'm doing wrong? Can attempt to provide more information if required.
Purdy8TV said:
Hi so I've spent a good deal of the morning attempting to finally fix this phone, a couple years ago I removed all OS from it and no backup but I still have TWRP.
The phone is tampered/unlocked.
Hboot is 1.54.0000
I tried loading one of the latest ROMS from here via side loading - http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
I used this guide - http://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/
Unfortunately once the sideload is complete I get an error E: Zio file is corrupt, I was wondering if anyone knows what I'm doing wrong? Can attempt to provide more information if required.
Click to expand...
Click to collapse
What recovery version do you have? Try flashing newest TWRP and give it a go
donkeykong1 said:
What recovery version do you have? Try flashing newest TWRP and give it a go
Click to expand...
Click to collapse
Hey thanks for the reply
This is the ROM I downloaded https://www.androidfilehost.com/?fid=95916177934554130
My recovery version is v2.6.0.1 for TWRP, should I upgrade?
You can't flash that via recovery. That's a RUU, and your phone must be in RUU mode and you flash it via recovery. Also, you're on very old firmware, so you need to flash all firmwares before that one. My suggestikn is to flash the latest recovery, and then flash a custom ROM. You can find custom ROMs on M7 android development thread
donkeykong1 said:
You can't flash that via recovery. That's a RUU, and your phone must be in RUU mode and you flash it via recovery. Also, you're on very old firmware, so you need to flash all firmwares before that one. My suggestikn is to flash the latest recovery, and then flash a custom ROM. You can find custom ROMs on M7 android development thread
Click to expand...
Click to collapse
Ah that would explain it lol, sadly very inexperienced with this.
Would there be a stock rom or just choose the one close to stock? (As in HTC sense one)
Purdy8TV said:
Ah that would explain it lol, sadly very inexperienced with this.
Would there be a stock rom or just choose the one close to stock? (As in HTC sense one)
Click to expand...
Click to collapse
I think there should be a stock rooted ROM, but you can flash pretty much any ROM from there. Most of them are stockish looking
donkeykong1 said:
I think there should be a stock rooted ROM, but you can flash pretty much any ROM from there. Most of them are stockish looking
Click to expand...
Click to collapse
Hey thanks very much for your speedy replies
Would this be okay then - http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927 ?
Also do I just sideload it as I attempted previously once TWRP is updated?
Purdy8TV said:
Hey thanks very much for your speedy replies
Would this be okay then - http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927 ?
Also do I just sideload it as I attempted previously once TWRP is updated?
Click to expand...
Click to collapse
Of all sense TOMs out there, you picked a GPE [emoji4] that's not Sense, but it will work.
New recoveries have MTP option, so you don't need sideload. Just mount MTP, and move your zip to your phone
donkeykong1 said:
Of all sense TOMs out there, you picked a GPE [emoji4] that's not Sense, but it will work.
New recoveries have MTP option, so you don't need sideload. Just mount MTP, and move your zip to your phone
Click to expand...
Click to collapse
Haha yeah, I did decide I actually preferred closer to stock android after using my Z3
I don't really know how to do that, will side loading still be okay? (I assumed this was my only option as I literally have no OS on my phone and just get stuck at the HTC loading screen when I turn phone on normally)
Purdy8TV said:
Haha yeah, I did decide I actually preferred closer to stock android after using my Z3
I don't really know how to do that, will side loading still be okay? (I assumed this was my only option as I literally have no OS on my phone and just get stuck at the HTC loading screen when I turn phone on normally)
Click to expand...
Click to collapse
MTP is much easier than sideload, and newer TWRP have it. You go into recovery (updated) and you will see "mount MTP" option. Click that, and your phone will show up on your PC. After that it's just drag and drop, but sideload will work too I think
donkeykong1 said:
MTP is much easier than sideload, and newer TWRP have it. You go into recovery (updated) and you will see "mount MTP" option. Click that, and your phone will show up on your PC. After that it's just drag and drop, but sideload will work too I think
Click to expand...
Click to collapse
Hmm
I can just see 'Mount' on the main TWRP page, then I go into that and see Cache/Data/devlog/System/USB OTG as check boxes and then just disable MTP button at the bottom.
Nothing showing on my macbook (not sure if that makes a difference as my w10 pc could not recognise the phone at all)
Purdy8TV said:
Hmm
I can just see 'Mount' on the main TWRP page, then I go into that and see Cache/Data/devlog/System/USB OTG as check boxes and then just disable MTP button at the bottom.
Nothing showing on my macbook (not sure if that makes a difference as my w10 pc could not recognise the phone at all)
Click to expand...
Click to collapse
Disable MTP is the one. Click it twice, and you're good to go
donkeykong1 said:
Disable MTP is the one. Click it twice, and you're good to go
Click to expand...
Click to collapse
Not showing up as a removable storage
Purdy8TV said:
Not showing up as a removable storage
Click to expand...
Click to collapse
Weird... Then go with sideload
donkeykong1 said:
Weird... Then go with sideload
Click to expand...
Click to collapse
Okay so I tried side loading, downloaded the google plus ROM from the link I posted, zipped it up and ended up getting this error.
Purdy8TV said:
Okay so I tried side loading, downloaded the google plus ROM from the link I posted, zipped it up and ended up getting this error.
Click to expand...
Click to collapse
That error means your adb tool is not working properly. At least that was the case on my PC. Can you try it on your windows machine?
donkeykong1 said:
That error means your adb tool is not working properly. At least that was the case on my PC. Can you try it on your windows machine?
Click to expand...
Click to collapse
Yeah I'll go give it another go on it.
It wouldn't be anything to do with the fact my device is tampered? (S Off I think?) Do I need something extra other than just the one link in the ROM I said i chose?
Purdy8TV said:
Yeah I'll go give it another go on it.
It wouldn't be anything to do with the fact my device is tampered? (S Off I think?) Do I need something extra other than just the one link in the ROM I said i chose?
Click to expand...
Click to collapse
You're s-off??? Go to your bootlader and confirm that please
donkeykong1 said:
You're s-off??? Go to your bootlader and confirm that please
Click to expand...
Click to collapse
Talking out my arse I'm S-ON lol, thought tampered meant S OFF lol, apologies
donkeykong1 said:
You're s-off??? Go to your bootlader and confirm that please
Click to expand...
Click to collapse
Okay so windows can detect the device it seems!
I see this, do I just delete the sideload.zip and then drag and drop the ROM I downloaded ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi everyone. Apparently I know just enough to get me in trouble. I received my new OnePlus 10 Pro 5G yesterday which I ordered thinking OnePlus phone were easy to root and mod. I was able to get the boot loader unlocked eventually, but then when I tried to root the phone I ended up in a boot loop. I can still get into to fastboot, lock and unlock my boot loader, but I can't get it to boot.
I found a rollback file for North America and was hoping to hopefully save my new phone by reflashing it.
Sorry for inexperience, I'm hoping there is a guide to doing this. I've been looking for hours
Thanks,
KB
For rooting our device we can use This guide, i don't know which model is you device but probably you can use the files provided there.
Now to solve your problem you need a stock boot.img file that match your current system version and flash it via fastboot
you are kind of sol. keep watching this thread and hopefully someone will post new login creds https://forum.xda-developers.com/t/edl-flash-tool-leak.4494211/
g96818 said:
you are kind of sol. keep watching this thread and hopefully someone will post new login creds https://forum.xda-developers.com/t/edl-flash-tool-leak.4494211/
Click to expand...
Click to collapse
That is what I was afraid of. I saw this thread before asking for help. There is just so much to sort through and hard to know
RokCruz said:
For rooting our device we can use This guide, i don't know which model is you device but probably you can use the files provided there.
Now to solve your problem you need a stock boot.img file that match your current system version and flash it via fastboot
Click to expand...
Click to collapse
My model is the NE2215. I found this rooting guide after following a bad rooting guide. I think the main difference is that the other one had me flash the patched boot.ini file and not boot from that file.
As far as stock boot image, I thought I found one in this thread https://community.oneplus.com/thread/1114712420498538501 for the Android 13 beta. It has a rollback package to revert to 12.
KB- said:
That is what I was afraid of. I saw this thread before asking for help. There is just so much to sort through and hard to know
My model is the NE2215. I found this rooting guide after following a bad rooting guide. I think the main difference is that the other one had me flash the patched boot.ini file and not boot from that file.
As far as stock boot image, I thought I found one in this thread https://community.oneplus.com/thread/1114712420498538501 for the Android 13 beta. It has a rollback package to revert to 12.
Click to expand...
Click to collapse
So you are on global ROM, do you remember which version? If it's the lastest version(NE2215_11_C.21) I can provide you with the stock boot.img
RokCruz said:
So you are on global ROM, do you remember which version? If it's the lastest version(NE2215_11_C.21) I can provide you with the stock boot
Click to expand...
Click to collapse
I had the August update I believe. It was the latest update.
KB- said:
That is what I was afraid of. I saw this thread before asking for help. There is just so much to sort through and hard to know
My model is the NE2215. I found this rooting guide after following a bad rooting guide. I think the main difference is that the other one had me flash the patched boot.ini file and not boot from that file.
As far as stock boot image, I thought I found one in this thread https://community.oneplus.com/thread/1114712420498538501 for the Android 13 beta. It has a rollback package to revert to 12.
Click to expand...
Click to collapse
Don’t know which version you’re on, but it’s best to follow the right guide for your model https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585/
All the stock boot files are there. Recommend you try booting each one until you find one that works, then validate your phone os version and flash the correct boot image.
May or may not work depending on your luck
KB- said:
I had the August update I believe. It was the latest update.
Click to expand...
Click to collapse
g96818 said:
Don’t know which version you’re on, but it’s best to follow the right guide for your model https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585/
All the stock boot files are there. Recommend you try booting each one until you find one that works, then validate your phone os version and flash the correct boot image.
May or may not work depending on your luck
Click to expand...
Click to collapse
As said here, download the stock boot from there and only boot it, it your device boots then flash that boot.img on fastboot or fastbootenhace
KB- said:
I had the August update I believe. It was the latest update.
Click to expand...
Click to collapse
I'm sorry, when you say version, I was assuming you meant which software update I had. Which version am I looking for?
RokCruz said:
As said here, download the stock boot from there and only boot it, it your device boots then flash that boot.img on fastboot or fastbootenhace
Click to expand...
Click to collapse
Sorry if these are dumb questions but I just want to make sure I'm doing it right.
I have downloaded both the global (6812ccee9a8a891032af1e053e3217731ac7ad92) and North American versions (2370_sign_NE2215_11_A_OTA_0130_all_bb1e47_10100001)
I have extracted them so I have the boot.img files as well. So you're saying I should run 'fastboot boot boot.img' and if it works, then I should do 'fastboot flash boot.img'?
KB- said:
Sorry if these are dumb questions but I just want to make sure I'm doing it right.
I have downloaded both the global (6812ccee9a8a891032af1e053e3217731ac7ad92) and North American versions (2370_sign_NE2215_11_A_OTA_0130_all_bb1e47_10100001)
I have extracted them so I have the boot.img files as well. So you're saying I should run 'fastboot boot boot.img' and if it works, then I should do 'fastboot flash boot.img'?
Click to expand...
Click to collapse
Yep that should be the procedure, the important thing is if that version match the current installed in your device, do you remember which android version you had? A13? A12?
RokCruz said:
Yep that should be the procedure, the important thing is if that version match the current installed in your device, do you remember which android version you had? A13? A12?
Click to expand...
Click to collapse
I don't know what version I had. I just tried to boot off both boot.img and both failed.
KB- said:
I don't know what version I had. I just tried to boot off both boot.img and both failed.
Click to expand...
Click to collapse
Quick settings look like this? How many updates did you installed?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
RokCruz said:
Quick settings look like this? How many updates did you installed?
View attachment 5767207
Click to expand...
Click to collapse
I can't get into my phone at all other than the fastboot screen.
KB- said:
I can't get into my phone at all other than the fastboot screen.
Click to expand...
Click to collapse
Yeah I know that but you almost see Q's once, anyway the only way that comes to my mind is flashing the full ROM via fastboot enhance for you device that should be NE2215_11_C21(Android 13)
For now i didn't used that tool, i upgraded my device via local update so I can't help with that
KB- said:
I can't get into my phone at all other than the fastboot screen.
Click to expand...
Click to collapse
RokCruz said:
Yeah I know that but you almost see Q's once, anyway the only way that comes to my mind is flashing the full ROM via fastboot enhance for you device that should be NE2215_11_C21(Android 13)
For now i didn't used that tool, i upgraded my device via local update so I can't help with that
Click to expand...
Click to collapse
Thank you for all your help. I think I've done about all I know how to do. I guess I'll just take it as an expensive lesson learned and hope that there is a way to do it in the future.
RokCruz said:
Yeah I know that but you almost see Q's once, anyway the only way that comes to my mind is flashing the full ROM via fastboot enhance for you device that should be NE2215_11_C21(Android 13)
For now i didn't used that tool, i upgraded my device via local update so I can't help with that
Click to expand...
Click to collapse
I've flashed a full firmware via Fastboot enhance after I installed a GSI..
I connected when in fastboot..
Deleted cow files, need to search then delete each one, then grabbed my most current full firmware payload.bin and flashed it.
Device booted fine, one part of it I need to be in Fastboot d, I think that was the cow files part. I could be remembering that part wrong though.
dladz said:
I've flashed a full firmware via Fastboot enhance after I installed a GSI..
I connected when in fastboot..
Deleted cow files, need to search then delete each one, then grabbed my most current full firmware payload.bin and flashed it.
Device booted fine, one part of it I need to be in Fastboot d, I think that was the cow files part. I could be remembering that part wrong though.
Click to expand...
Click to collapse
@KB- that should fix your issue.
@dladz I guess the patched boot.img needs to be flashed in fastbootd instead bootloader? to avoid bootloops anyway better to just boot it.
RokCruz said:
@KB- that should fix your issue.
@dladz I guess the patched boot.img needs to be flashed in fastbootd instead bootloader? to avoid bootloops anyway better to just boot it.
Click to expand...
Click to collapse
If it's within a payload then no it's integrity is intact.
If it's been extracted to be patched then yes booting is preferred, but there's no option in Fastboot enhance for that.
RokCruz said:
@KB- that should fix your issue.
@dladz I guess the patched boot.img needs to be flashed in fastbootd instead bootloader? to avoid bootloops anyway better to just boot it.
Click to expand...
Click to collapse
Thank you for the advice. Is there a tutorial on how to do all this? I feel like I'm just making it worse since I don't know enough