Related
So I'm not fluent in the linux terminal. I'm basically illiterate, deaf and dumb. So here I am trying to root using toasts tutorial, How To Root The HTC EVO ~ Part-1 \0/
the forum won't let me post links yet., and apparently the software here thinks some part of the code I'm posting is a link.
Anyway I'm at this step,
- At this point it will boot into a rooted rom.
- YOU ARE NOW ROOT!!!
- rename the PC36IMG.zip on your sdcard:
- plug your phone into a usb port on your desktop and do:
Click to expand...
Click to collapse
I may be root but I had a problem and had to redo this step... my sdcard was not being recognized. After reflashing/ updating I was able to access it again.
Now this rename the zip file step... I'm thinking if I rename it the code I'm supposed to enter isn't going to work. What should I rename it to?
How should I enter this code? first off my sd card isn't called sdcard it's called an 8 digit number.
I tried this (can't post the code for some reason) without changing the name of the zip file. I'm thinking I don't have the locations right because I know the file is in there.
I need some direction to get to the next step.
Thanks
Mods please move this thread....
to wherever it will get the most or correct exposure. Sorry if I put it in the wrong place.
i have no idea what your doing...i rooted via the unREVOked method...i had to downgrade to 2.1, then actually root...can u send me a PM with what tutorial your following? and also the current info you have for your phone, like what its running (2.1 or 2.2) and stuff of that nature.... we shall see if i can help, not sure but its worth a shot
okay form what i read you have already flashed the .zip. Make sure you clear your data and cache as these will cause boot loops if not cleared. Also you can rename the .zip to anything you want, this just makes it so the bootloader does not try to install the .zip a second time.
oshizzle1991 said:
i have no idea what your doing...i rooted via the unREVOked method...i had to downgrade to 2.1, then actually root...can u send me a PM with what tutorial your following? and also the current info you have for your phone, like what its running (2.1 or 2.2) and stuff of that nature.... we shall see if i can help, not sure but its worth a shot
Click to expand...
Click to collapse
I'm running 2.1. I never upgraded. The tutorial I'm following is in thread #690762 I'll try to pm the link but I don't think they'll let me. I thought unrevoked wasn't a full root. I want to unlock nand. I'm also using Ubuntu here, not windows.
http://forum.xda-developers.com/showthread.php?t=690762
nfaust01 said:
okay form what i read you have already flashed the .zip. Also you can rename the .zip to anything you want, this just makes it so the bootloader does not try to install the .zip a second time.
Click to expand...
Click to collapse
Nice looks like I'm allowed to put up links now... Thanks!
Yes I flashed the .zip my phone called it "updating" when it was going on.
Make sure you clear your data and cache as these will cause boot loops if not cleared.
Click to expand...
Click to collapse
Do I do that from the boot menu?
Also you can rename the .zip to anything you want, this just makes it so the bootloader does not try to install the .zip a second time.
Click to expand...
Click to collapse
I just removed the .zip part. What is the point of the next step, which I couldn't get to work, if I rename the file?
Code:
adb shell mv /sdcard/PC36IMG.zip /sdcard/root-PC36IMG.zip
Well I guess I'm going to start over and wait for the latest unrevoked to come back out. Thanks to everyone that tried to help. "NO ROOT FOR YOU!"
You have a lot to learn....
First of all, don't rename the sdcard, rename pc36img.zip. Just rename it to anything you want so boat loader doesn't recognize it and try to update itself. Next, you aren't utilizing root. You do have a rooted boot loader, but you are still using a protected recovery and rom. Install a custom recovery and flash a new rom so you can be cool.
dkdude36 said:
First of all, don't rename the sdcard, rename pc36img.zip
Click to expand...
Click to collapse
Yes, I know I have a lot to learn. I didn't rename the sdcard, that wasn't possible. I figured part of the problem with getting this to work was the path. My sdcard wasn't called sdcard it was called some 8 digit number. I eventually worked around pushing the file to the sd card by installing the phone as a drive and dragging the file to the sdcard.
Just rename it to anything you want so boat loader doesn't recognize it and try to update itself.
Click to expand...
Click to collapse
After I rebooted and updated/ flashed the file, I renamed the file on the sdcard by removing the .zip. I did this via disk drive on my laptop because I wasn't getting anywhere with the command line.
Again this part didn't make any sense to me, not that most of it does, but what was the point of the next command in the directions if I renamed the file?
Next, you aren't utilizing root. You do have a rooted boot loader, but you are still using a protected recovery and rom. Install a custom recovery and flash a new rom so you can be cool.
Click to expand...
Click to collapse
Right "I have a lot to learn" I thought following the directions in toasts tutorial step by step would have gotten me to that point. I didn't realize I was just supposed to skip stuff when I run into problems. That kinda seems like what your telling me to do. I thought all of the commands were important.
I was hoping you had some follow up insight dkdude.
if you still on 2.1, try this method (just make sure the files aren't corrupted)
http://forum.xda-developers.com/showthread.php?t=741294
So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
WARNING!
I'm no dev, just someone, that knows linux.
If you follow this path, you do it on your own. I'm not responsible for bricked devices, lost data or whatsoever, including the future the past and the present.
Click to expand...
Click to collapse
There are three ways for you, to make an md5 sum of the img files, the good and the bad one and also the quoted one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
cd /sdcard/clockworkmod/backup/{recovery_timestamped_directory} <- this is from your backup, so you need to fill in appropirate data
md5sum *img > nandroid.md5
Click to expand...
Click to collapse
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
.android_secure.vfat.tar
boot.img
data.ext4.tar
{nandroid.md5}
recovery.img
system.ext4.tar
Click to expand...
Click to collapse
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
Three (the quoted one)
Also on the 2nd page you will find an alternative solution for the problem which can help you if you have got busybox installed on your device.
The solution resembles the One type of fix, so with quotes here's the one (thanx for Meeshka for it).
Meeshka said:
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
Click to expand...
Click to collapse
If I helped, don't hesitate to push the Thanks button.
Thanks... a very useful guide. Bookmarked
WORKED!!! Tho I'm from a different device the first (adb) method saved my AOKP backup!!! Daysaver I'd say!!
I keep getting "md5sum: not found"
Put this in the general android section as it works across most devices. ..
Sent from my One V
Nevell said:
I keep getting "md5sum: not found"
Click to expand...
Click to collapse
if you send me the 2 img files i can create an appropirate md5 image of them, but send the one you did, so I can guess what the problem is.
send them to the email of my usr here, or in pm. and mainly, the md5 image has the name "nandroid.md5" like small caption all the way, even the md5? If it is there where it must, it must work, ad absurd it will be "wrong checksum error", but that is another version.
General android section has this, I have learned this from there, but it had only 1st option, and was "discovered" when cwm had generated wrong md5s, the V, in the V the problem is a tad bit different, but the solution is the same.
I fixed it in adb
Sent from my SPH-L710 using xda premium
Nevell said:
I fixed it in adb
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Can you explain what did you do to fix md5sum: not found error??
please i need it!
thatsgamer said:
Can you explain what did you do to fix md5sum: not found error??
please i need it!
Click to expand...
Click to collapse
Just created an md5sum manualy from the img files with the name of nandroid.md5, because on the V the recovery doesn't creates them because of cache mount problem.
The recovery process will end in an error message, because cache cannot be recovered, but the main thing will be recovered this way.
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
haky1988 said:
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
Click to expand...
Click to collapse
See : http://forum.xda-developers.com/showpost.php?p=32248108&postcount=7
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
CWM showing different versions
-Delete-
maranello69 said:
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
Click to expand...
Click to collapse
You do know that the first method is exactly like the one you linked right?
Aside that, I'm happy that the community could help you out
Loir can u help me. I can't locate the boot.img inside the downloads for cyanogen mod u provided. Forgive me but can you post a directory to this kernel file? Tks
Sent from my HTC Desire X using xda app-developers app
Thank you so much. You saved my phone.
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
no * 's
Ken-Shi_Kun said:
So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
There are two ways for you, to make an md5 sum of the img files, the good and the bad one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
If I helped, don't hesitate to push the Thanks button.
Click to expand...
Click to collapse
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Beastben13 said:
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Click to expand...
Click to collapse
I have done the thing with a legacy tcmd, so there is a probability, that they have modified the md5sum algorithm, so if you don't se the stars don't panic. (also it should do the trick even with stars in the file, but wanted to be sure at the time I wrote the post)
plz provide touch recovery for karbon a9+ plz and ther is bugs in cwm recovery 5.0.2.8 plz
I just recently picked up a evo 4g wimax from a buddy of mine that recently updated to a gs3 and I am trying to achieve unlocked/s-off. I am using this guide http://forum.xda-developers.com/showthread.php?t=1771755 and The zip file I downloaded from the thread contains a pc36img, The only thing though is every time I download from that thread the pc36img is corrupt and I can not find a download link that is working anymore. I did find this other guide http://themikmik.com/showthread.php...18-HBOOT-with-HTCDev-com-No-More-Watermark!-) that has a few pc36img files available to be downloaded but I tried http://d-h.st/XJX that one and the same thing happened, the downloaded zip file is corrupt. Can anyone help me out or point me in the right direction?
http://forum.xda-developers.com/showthread.php?t=1661543
Sent using my HTC EVO LTE and a magic wand
droidjunkie said:
I just recently picked up a evo 4g wimax from a buddy of mine that recently updated to a gs3 and I am trying to achieve unlocked/s-off. I am using this guide http://forum.xda-developers.com/showthread.php?t=1771755 and The zip file I downloaded from the thread contains a pc36img, The only thing though is every time I download from that thread the pc36img is corrupt and I can not find a download link that is working anymore. I did find this other guide http://themikmik.com/showthread.php...18-HBOOT-with-HTCDev-com-No-More-Watermark!-) that has a few pc36img files available to be downloaded but I tried http://d-h.st/XJX that one and the same thing happened, the downloaded zip file is corrupt. Can anyone help me out or point me in the right direction?
Click to expand...
Click to collapse
If you mean that RootEvo4Gnew.zip file:
https://dl.dropbox.com/u/38127313/RootEvo4GNew.zip
The PC36IMG.zip file that you are looking for is inside the RootEvo4GNew.zip file. Right now, it just needs time to upload.
shortydoggg said:
If you mean that RootEvo4Gnew.zip file:
https://dl.dropbox.com/u/38127313/RootEvo4GNew.zip
The PC36IMG.zip file that you are looking for is inside the RootEvo4GNew.zip file. Right now, it just needs time to upload.
Click to expand...
Click to collapse
Like I said, I know where its at, and everytime i download that zip file with the pc36img from the thread and extract the files everything is fine except for the pc36img which is somehow corrupt.
I tried your download link for the zip file and I just get sent to a dropbox 404 page.
FinZ28 said:
http://forum.xda-developers.com/showthread.php?t=1661543
Sent using my HTC EVO LTE and a magic wand
Click to expand...
Click to collapse
I am confused as to why you linked me to that thread, I am looking for a specific pc36img that will downgrade me and allow me to achieve s-off. The only thing available in that link is a recovery img which I do not need.
droidjunkie said:
I am confused as to why you linked me to that thread, I am looking for a specific pc36img that will downgrade me and allow me to achieve s-off. The only thing available in that link is a recovery img which I do not need.
Click to expand...
Click to collapse
Sorry, I misread your post. It was a long night at work last night, not always the best time for troubleshooting
Sent using my HTC EVO LTE and a magic wand
droidjunkie said:
Like I said, I know where its at, and everytime i download that zip file with the pc36img from the thread and extract the files everything is fine except for the pc36img which is somehow corrupt.
I tried your download link for the zip file and I just get sent to a dropbox 404 page.
Click to expand...
Click to collapse
Well, I know that.
That's why I said in the post that it needed time to upload. It should be OK now.
shortydoggg said:
Well, I know that.
That's why I said in the post that it needed time to upload. It should be OK now.
Click to expand...
Click to collapse
ok, I am downloading one from every location I know on a different computer to see if its my computer causing the problems
droidjunkie said:
ok, I am downloading one from every location I know on a different computer to see if its my computer causing the problems
Click to expand...
Click to collapse
Downloaded from a different computer and still the same issue, file is corrupt. Trying to check the md5 value and it does not even give me a md5 at all matching or not. I am going to go to a friends house and try downloading it again.
Ok, I have tried from a 3 different computers, my tablet and my htc thunderbolt and everytime it ends up in a corrupt/invalid .zip file. Can anyone link me to a known good working file so I can downgrade my hboot and get s-off?
droidjunkie said:
Ok, I have tried from a 3 different computers, my tablet and my htc thunderbolt and everytime it ends up in a corrupt/invalid .zip file. Can anyone link me to a known good working file so I can downgrade my hboot and get s-off?
Click to expand...
Click to collapse
You downloaded from 3 different computers, probably through the same connection, but I believe you tried to run them from the same computer that failed every time, just a guess.
Just tried 2 of the links:
http://d-h.st/XJX
https://dl.dropbox.com/u/38127313/RootEvo4GNew.zip
and I'm currently in the process of trying the 3rd.
http://downloadandroidrom.com/file/H...otEvo4GNew.zip from your link here: http://forum.xda-developers.com/show....php?t=1771755
They work just fine. The problem appears to be on your end. All three downloads are OK.
And if that's not the case, here is the same file that I have been using since last year that others have downloaded. So if this one fails as well, then yes, there is definitely something wrong on your end.
https://dl.dropbox.com/u/38127313/P....15.00.0808_NV_2.15_release_220182_signed.zip
Also, I'm going to downgrade and S-OFF my old Evo with the same files just to verify that they are OK.
droidjunkie said:
Ok, I have tried from a 3 different computers, my tablet and my htc thunderbolt and everytime it ends up in a corrupt/invalid .zip file. Can anyone link me to a known good working file so I can downgrade my hboot and get s-off?
Click to expand...
Click to collapse
Stop trying to open the zip files and you'll be fine . The ones in my thread are fine, as was mentioned.
In the past with my thunderbolt and downloading the same files I have noticed if I can not open the zip file and see what is in it then it will not properly flash. But just for the sake of argument I will do it your way.
Sent from my ADR6400L using xda app-developers app
droidjunkie said:
In the past with my thunderbolt and downloading the same files I have noticed if I can not open the zip file and see what is in it then it will not properly flash. But just for the sake of argument I will do it your way.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
If you have to you could always download the froyo RUU and pull the rom.zip from it, rename to PC36IMG.zip and flash
To do this, run the RUU but do not click anything after it opens
With the RUU still open, open a "Run..." window (WindowsKey + R) and type in "%temp%" then enter to go to your temporary files folder
Sort the files by date modified and go into the most recent folders, find a zip called "rom.zip" and copy that to your desktop
Close the RUU, rename the "rom.zip" to "PC36IMG.zip" and you can then flash it through bootloader
Sent from my PG06100
Yep, the downloads do work. There is nothing wrong with any of the files. Phone went from 2.18, S-ON to 6.16, S-OFF without any issues from those same downloads.
---------- Post added at 11:25 AM ---------- Previous post was at 11:22 AM ----------
CNexus said:
If you have to you could always download the froyo RUU and pull the rom.zip from it, rename to PC36IMG.zip and flash
To do this, run the RUU but do not click anything after it opens
With the RUU still open, open a "Run..." window (WindowsKey + R) and type in "%temp%" then enter to go to your temporary files folder
Sort the files by date modified and go into the most recent folders, find a zip called "rom.zip" and copy that to your desktop
Close the RUU, rename the "rom.zip" to "PC36IMG.zip" and you can then flash it through bootloader
Sent from my PG06100
Click to expand...
Click to collapse
I forgot about that trick, although I think I use to do it slightly different.
Captain_Throwback said:
Stop trying to open the zip files and you'll be fine . The ones in my thread are fine, as was mentioned.
Click to expand...
Click to collapse
I also forgot to mention that before trying to open them to see if it was corrupt or not I try to check the md5 of the zip file, it does not even give me a md5 it also says the files are corrupt. I will try again though
I'm having the same problem. I just finished repairing my old EVO and looking to downgrade it to 2.15. All the links have bad files. Tried D/L from work, friends house, parents, and to my SGS3. Always get the same message..."cant open the folder... zipped folder is invalid." I've been to numerous sites about this and i'm always directed to the same files. This isn't a rare issue, it's a lot of people. There's something wrong with those files.
harry46222 said:
I'm having the same problem. I just finished repairing my old EVO and looking to downgrade it to 2.15. All the links have bad files. Tried D/L from work, friends house, parents, and to my SGS3. Always get the same message..."cant open the folder... zipped folder is invalid." I've been to numerous sites about this and i'm always directed to the same files. This isn't a rare issue, it's a lot of people. There's something wrong with those files.
Click to expand...
Click to collapse
No, there isn't. The zip files are encrypted, so most zip programs will throw an error if you try to open them. They should not be unzipped. The files from my post have always and still work fine. Just follow the instructions and stop trying to open the zip!
NOTE: Some browsers will try to automatically open the zip file when download is complete. In that case, try a different browser.
No go, sir. Opening the zip or not, the fact is it doesn't work. I have a few of these files and none of them are recognized when boot loader is brought back up to flash the file. It scans the zip, can't find file, image or anything. Its the same thing no matter which one I use. I'll keep looking for a good procedure and a decent download.
harry46222 said:
No go, sir. Opening the zip or not, the fact is it doesn't work. I have a few of these files and none of them are recognized when boot loader is brought back up to flash the file. It scans the zip, can't find file, image or anything. Its the same thing no matter which one I use. I'll keep looking for a good procedure and a decent download.
Click to expand...
Click to collapse
There's nothing wrong with Captain's files or the pc36img.zip files given on this page. They work just fine as usual. I just downloaded one (again) and confirmed it.
Is your phone S-Off? Did you flash a mtd-eng.img file to your misc partition, so that it will downgrade?
If you answer no to both of these questions, then the problem is not necessarily the zip files, but is likely on your end. And if you answered no to both of those questions, then the zip files are not likely going to work for you.
And, if one of your answers is yes, then it could be a problem with your sdcard. Sometimes they are full, or not formated correctly, or have some other issue, which will also cause the files to fail. You cannot always assume that just because a file does not work the way you expect it to, that it is necessarily something wrong with that file.
Hello as suggested by ''Sawdoctor" (scary name btw.) I post my original from XDA Assist right here.
Okay guys I know this title isn't the best. But I don't want you to delete me because it has been already made. Because I DON'T EVEN KNOW WHAT THE HECK THE PROBLEM IS.
Alright Phone : HTC One M9 (1,5 years old)
After downloading an app from google play ''Spy Camera OS 3 (SC-OS3)'' , I guess someone from you guys developed it. No idea. I don't even know if it was this app that caused it. BUT - after I downloaded it and used for a while other apps started crashing ( for example : Facebook, Instagram). So I thought oh wow. I reset my phone and it will fix everything( dummy me) . Ye I did restart it and ended up in this funny screen ( maybe you would call it BOOTLOADER ? no idea)
It says tho :
***Software status : Modified***
*** LOCKED ***
*** S-ON ***
*** SECURITY WARNING***
/*<VOL UP> to previous item <VOL DOWN> to next item<POWER> to select item */
REBOOT
REBOOT TO BOOTLOADER
BOOT TO DOWNLOAD MODE
BOOT TO RECOVERY MODE
POWER DOWN
I have only tried those that are green colored and ended up back there where I started. Any ideas ? I am rookie. I have never done a root on my phones. No idea how to do it. So explain to me like to a kid. Thanks a lot.
Unfortunately just after 10 posts I can add pics. Hope you can help without seeing what I see.
Either a failed root attempt or a borked nand. The app didn't cause it.
Beamed in by telepathy.
shivadow said:
Either a failed root attempt or a borked nand. The app didn't cause it.
Beamed in by telepathy.
Click to expand...
Click to collapse
Alright man, I am telling you I have never done root on my devices !! Because I know you can **** your phone up and I never wanted that.
I simply restarted phone. Turned on. This came up. Don't even know how to root.
I think (hopefully) the problem can be solved by re-flashing stock ROM. You just need to find correct RUU.zip file for your device. Rename this zip file as 0PJAIMG.zip and put zip file in your microSD card. Power off your phone. Put microSD card. Press and hold vol- and power button simultaneously (it will boot to download mode and try to install zip file in SD card). Let me know the result
oscar_ferreiro said:
I think (hopefully) the problem can be solved by re-flashing stock ROM. You just need to find correct RUU.zip file for your device. Rename this zip file as 0PJAIMG.zip and put zip file in your microSD card. Power off your phone. Put microSD card. Press and hold vol- and power button simultaneously (it will boot to download mode and try to install zip file in SD card). Let me know the result
Click to expand...
Click to collapse
Hello, great suggestion. I am going to try it. One more question to it. Do I place it in specific folder in SD card so the phones reads the .zip file first ??
Let's try this ! Hopefully it works.
Btw. is there a difference restoring it from RUU.zip file and RUU.exe file ??
EDIT: Well I just realized, I don't have any USB connector for SD cards nor available android phone to put the file via that (only iPhones at home right now) . I am going to try it tommorow and hopefull it works.
YoYiXxX said:
Hello, great suggestion. I am going to try it. One more question to it. Do I place it in specific folder in SD card so the phones reads the .zip file first ??
Let's try this ! Hopefully it works.
Btw. is there a difference restoring it from RUU.zip file and RUU.exe file ??
Click to expand...
Click to collapse
Well, place it on root folder. And better to have empty SD card. So there will be only that file
About second question, I think there is no difference. Have not found proper RUU.exe for mine, so have not experienced restoring from it
oscar_ferreiro said:
Well, place it on root folder. And better to have empty SD card. So there will be only that file
About second question, I think there is no difference. Have not found proper RUU.exe for mine, so have not experienced restoring from it
Click to expand...
Click to collapse
Last question what exactly am I looking for in .ZIP file ? When my release date was Dec 17 2015, 0:40:10, can I use another ? With the same OS ( 3.35.161.12) and RADIO(01.01_U11440792_96.00.51201G_F) info, which I think is more important. I don't know what exactly has to be the same in the RUU file and what can difffer and is not that important. Thanks in advance
YoYiXxX said:
Last question what exactly am I looking for in .exe file ? When my release date was Dec 17 2015, 0:40:10, can I use another ? With the same OS ( 3.35.161.12) and RADIO(01.01_U11440792_96.00.51201G_F) info, which I think is more important. I don't know what exactly has to be the same in the RUU file and what can difffer and is not that important. Thanks in advance
Click to expand...
Click to collapse
In order to succeed, you should chose by following criteria:
- RUU software version equal or higher than what's on the phone (as it is S-On in your condition)
- MID should match
- CID should match
- HTC Syncmanager (for drivers if you are going to use exe file)
- Some other miscellaneous things that are most of PC already have pre-installed (again for exe file)
oscar_ferreiro said:
In order to succeed, you should chose by following criteria:
- RUU software version equal or higher than what's on the phone (as it is S-On in your condition)
- MID should match
- CID should match
- HTC Syncmanager (for drivers if you are going to use exe file)
- Some other miscellaneous things that are most of PC already have pre-installed (again for exe file)
Click to expand...
Click to collapse
my phone says following :
***LOCKED***
htc_himauhl PVT S-ON
LK-1.0.0.0000
RADIO-01.01_U11440792_96.00.51201G_F
OpenDSP-15.6.1.00522.8994_1026
OS-3.35.161.12
Dec 17 2015, 00:40:10(671447)
The matching file I downloaded says :
0PJAIMG_HIMA_UHL_M60_SENSE70_MR_Vodafone_UK_3.35.161.12_Radio_01.01_U11440792_96.00.51201G_F_release_464298_signed.zip
Cyan colored I see matches. Only release date, UK( I have the phone from Germany Vodafone) don't match. M60 I don't really understand, what that stands for.
IT WORKED
Big thanks to user : oscar_ferreiro
Your suggestion worked. I am back in my phone. You're boss. Hopefully it won't stop working in following days.
Thanks a lot. Have a nice day. XDA forever.
-YoYiXxX
Very glad that could help you. Please don't forget to hit the "Thanks!" button under my post. Good luck and hope your phone will last long
YoYiXxX said:
Alright man, I am telling you I have never done root on my devices !! Because I know you can **** your phone up and I never wanted that.
I simply restarted phone. Turned on. This came up. Don't even know how to root.
Click to expand...
Click to collapse
Then it's a borked nand. Before you flash anything blindly I suggest you spend a day or two reading about possible errors you may encounter and how to resolve them.
Good luck!.
Beamed in by telepathy.
F*ck this...
Alright listen, here we are 4 days later ... again out of nowhere !! my phone started crashing every single app.. EVERY single app, no app would work for me... I knew that if I do turn off my phone the same screen pops up with that ''Reboot'' stuff.. so I did turn the phone off ( IT DID VIBRATE BEFORE THE SCREEN COMPLETELY WENT OFF, if that's a trigger to someone) and the ''Reboot' white screen popped up as expected. WHAT THE F*CK ANDROID. I HAVE NEVER EXPERIENCED SOMETHING LIKE THIS.
I don't know what kind of virus can that be or whatever. I know that if I use the file I used before to reload the Stock ROM it will somehow work, but as you can see only for couple days. I didn't do anything to cause it in terms of trying to root my phone. Trust me.
Anyone willing to help ?
shivadow said:
Then it's a borked nand. Before you flash anything blindly I suggest you spend a day or two reading about possible errors you may encounter and how to resolve them.
Good luck!.
Beamed in by telepathy.
Click to expand...
Click to collapse
Yes I will do the research. Thought you just threw nonsense words with that ''borked nand".
I just downloaded to my XT1575 and I don't know which directory it downloaded to? Any ideas?
glfngmble said:
I just downloaded to my XT1575 and I don't know which directory it downloaded to? Any ideas?
Click to expand...
Click to collapse
/data/data/org.lineageos.updater/app_updates
jhedfors said:
/data/data/org.lineageos.updater/app_updates
Click to expand...
Click to collapse
Thank You.
There is no folder /app_updates. There is just a folder named "files", but this folder is completely empty.
By the way: I got this file structure on my G4: \Android\data\org.lineageos.updater\files.
I had to manually download the package and install it manually in recovery, but the updater says still to update the current version.
rigattoni said:
There is no folder /app_updates. There is just a folder named "files", but this folder is completely empty.
By the way: I got this file structure on my G4: \Android\data\org.lineageos.updater\files.
I had to manually download the package and install it manually in recovery, but the updater says still to update the current version.
Click to expand...
Click to collapse
/data/data/org.lineageos.updater/app_updates
The updater does not recognize what version is installed, just if the update is in the folder.
jhedfors said:
/data/data/org.lineageos.updater/app_updates
The updater does not recognize what version is installed, just if the update is in the folder.
Click to expand...
Click to collapse
If this is reduced to this single folder I can say that my G4 has no folder with this name.
The download completed and the updater asks for updating the unit.
The G4 restarts into recovery mode and nothing happens. Manual search for the downloaded files have not been successful.
I restarted my G4 and searched manually with root rights (just to be sure the files are not hidden in non root search) and I could not find any update file.
The lineage updater still shows to update the phone, even that there whether is a folder named "/data/org.lineageos.updater/app_updates"
nor a file in the "\data\org.lineageos.updater\files.
So... is this an issue with the updater, ROM or is this just not implemented complete?
I have no issues to manually install anything by console or TWRP or what ever else.
Once again: The update file(s) seem to be lost in transit. They are not stored on the system.
The updater still shows the install button even if there is nothing to install.
rigattoni said:
If this is reduced to this single folder I can say that my G4 has no folder with this name.
The download completed and the updater asks for updating the unit.
The G4 restarts into recovery mode and nothing happens. Manual search for the downloaded files have not been successful.
I restarted my G4 and searched manually with root rights (just to be sure the files are not hidden in non root search) and I could not find any update file.
The lineage updater still shows to update the phone, even that there whether is a folder named "/data/org.lineageos.updater/app_updates"
nor a file in the "\data\org.lineageos.updater\files.
So... is this an issue with the updater, ROM or is this just not implemented complete?
I have no issues to manually install anything by console or TWRP or what ever else.
Once again: The update file(s) seem to be lost in transit. They are not stored on the system.
The updater still shows the install button even if there is nothing to install.
Click to expand...
Click to collapse
Are you sure you are looking in the right folder? Your stated path shows :
"\data\org.lineageos.updater"
Was that just a typo?
This where it is in my device:
"/data/data/org.lineageos.updater/app_updates" (note the nested "data" in "data")
Also, I think that if it shows "install" it means that it has been downloaded (and exist), otherwise it would show "download".
jhedfors said:
Are you sure you are looking in the right folder? Your stated path shows :
"\data\org.lineageos.updater"
Was that just a typo?
This where it is in my device:
"/data/data/org.lineageos.updater/app_updates" (note the nested "data" in "data")
Also, I think that if it shows "install" it means that it has been downloaded (and exist), otherwise it would show "download".
Click to expand...
Click to collapse
Shame on me... I searched with root rights and could not find the folder.... Seems I need new glasses.
But the folder is there and yes, the download is in there.
So single issue is, why the updater does not call the update automatically for flashing the update.
rigattoni said:
Shame on me... I searched with root rights and could not find the folder.... Seems I need new glasses.
But the folder is there and yes, the download is in there.
So single issue is, why the updater does not call the update automatically for flashing the update.
Click to expand...
Click to collapse
Hmmm... TWRP should be able to handle the script created by the updater. You may want to check on the G4 forum to see if others have the same issue.
jhedfors said:
Hmmm... TWRP should be able to handle the script created by the updater. You may want to check on the G4 forum to see if others have the same issue.
Click to expand...
Click to collapse
the guys in the G4 forum are mostly connected to the unofficial version. a complete manual installation is required.
But there are some rumors in the German forum, who are using the official LineAgeOS version, where the updater script is not working.
I´ll wait for the next update in a week... may be it´s just a minor issue which will be fixed soon.
is it possible to change that path?
The path *HAS* been changed.
It's now downloading OTA updates to /data/lineageos_updates
Which a pain in the ass, because TWRP already doesn't automatically handle the script as expected on my Note3, and, I'd already gotten used to having to go to /data/data/org.lineageos.updates.
Hrmph.
darrylhadfield said:
The path *HAS* been changed.
It's now downloading OTA updates to /data/lineageos_updates
Which a pain in the ass, because TWRP already doesn't automatically handle the script as expected on my Note3, and, I'd already gotten used to having to go to /data/data/org.lineageos.updates.
Hrmph.
Click to expand...
Click to collapse
Thank you!!!! :victory::victory::victory: It works!!
rarmz said:
Thank you!!!! :victory::victory::victory: It works!!
Click to expand...
Click to collapse
Happy to help!
Now, if I can just get the attention of whoever the device maintainer is, for the Note3, to figure out the TWRP scripting issue...