i have CustomerID error after flash mokee rom and every time i reboot my phone i must use BP Tools
the error message is " customerid error.contact dealer boot to suspend/tcmd mode.dead.00004.00000000000000.000000000cc" when reboot
"mmcblk1p18" file needed for Retail Southafrica/UAE
it can be found on this direction "/dev/block/mmcblk1p18"
any help please?
CID err
First: For Atrix 2 cid.img is in /dev/block/mmcblk1p19.
Second: If you screwed cid & don't have backup - we can't help for you, because cid.img is unique for every phone, so if you screwed cid you can only bypass it.
Boot it using BP Tools. To bypass it you'll need root it (when rooting program reboot your phone hold vol down+up buttons & choose bp tools) (in short when screen turns black). Download BMM from Playstore & install it. BMM will bypass CustomerID error using 2ndinit...
turffe said:
First: For Atrix 2 cid.img is in /dev/block/mmcblk1p19.
Second: If you screwed cid & don't have backup - we can't help for you, because cid.img is unique for every phone, so if you screwed cid you can only bypass it.
Boot it using BP Tools. To bypass it you'll need root it (when rooting program reboot your phone hold vol down+up buttons & choose bp tools) (in short when screen turns black). Download BMM from Playstore & install it. BMM will bypass CustomerID error using 2ndinit...
Click to expand...
Click to collapse
Hmmmm ...
thx alot ... but ... r u sure about this??? :'(
CID err again...
finalfantasy1st said:
Hmmmm ...
thx alot ... but ... r u sure about this??? :'(
Click to expand...
Click to collapse
Yes I'm 100% sure about this. For more info read again my post behind you & for more explained info read this Razr thread about Jelly Bean. Post: http://forum.xda-developers.com/showpost.php?p=36172192&postcount=1
Helpful info: 1.Backup your cid using terminal emulator.
code: dd if=/dev/block/mmcblk1p18 of=/sdcard/cid.img (remember this code is case sensitive, copy the code correctly with proper and exact spaces in the lines)
Q. Why to do that?
A. You cannot flash kernel from different region because is protected by MOTO.
When you erase CID partition you can flash US kernel to EU device
every single one device has unique CID number so you have to backup CID partition before you erase it. If you not backup you're not able to restore your unique CID number and you can only boot your device via Power ON + Vol+ Vol- then BP Tools.
This is temporary solution, when Moto release European 4.1.2 most of us restore CID from Backup then we will flash EU kernel and EU system.
turffe said:
Yes I'm 100% sure about this. For more info read again my post behind you & for more explained info read this Razr thread about Jelly Bean. Post: http://forum.xda-developers.com/showpost.php?p=36172192&postcount=1
Helpful info: 1.Backup your cid using terminal emulator.
code: dd if=/dev/block/mmcblk1p18 of=/sdcard/cid.img (remember this code is case sensitive, copy the code correctly with proper and exact spaces in the lines)
Q. Why to do that?
A. You cannot flash kernel from different region because is protected by MOTO.
When you erase CID partition you can flash US kernel to EU device
every single one device has unique CID number so you have to backup CID partition before you erase it. If you not backup you're not able to restore your unique CID number and you can only boot your device via Power ON + Vol+ Vol- then BP Tools.
This is temporary solution, when Moto release European 4.1.2 most of us restore CID from Backup then we will flash EU kernel and EU system.
Click to expand...
Click to collapse
Hmmm ... first of all my device is atrix 2 ...
look l found the files "mmcblk1p18" and "mmcblk1p19" on the direction /dev/block
this means i didn't lose my cid.img or not ?? and which one contains cid.img ??
and if cid.img still here ... how can i fix this error???
finalfantasy1st said:
Hmmm ... first of all my device is atrix 2 ...
look l found the files "mmcblk1p18" and "mmcblk1p19" on the direction /dev/block
this means i didn't lose my cid.img or not ?? and which one contains cid.img ??
and if cid.img still here ... how can i fix this error???
Click to expand...
Click to collapse
Only if you maded backup via BMM or via Terminal.... If in this partition is still some files, than this doesnt mean that you can solve this problem... Problem is erased CID.... So if you don't have backup than your screwed... & also CID is not in ANY fxz or fastboot files... it's unique number for every device....
finalfantasy1st said:
Hmmm ... first of all my device is atrix 2 ...
look l found the files "mmcblk1p18" and "mmcblk1p19" on the direction /dev/block
this means i didn't lose my cid.img or not ?? and which one contains cid.img ??
and if cid.img still here ... how can i fix this error???
Click to expand...
Click to collapse
if your phone stated that CID is gone, then its gone, Without a backup of it, your SOL.
workaround is BP tools as stated above. Tho I have never done it.
turffe said:
Only if you maded backup via BMM or via Terminal.... If in this partition is still some files, than this doesnt mean that you can solve this problem... Problem is erased CID.... So if you don't have backup than your screwed... & also CID is not in ANY fxz or fastboot files... it's unique number for every device....
Click to expand...
Click to collapse
Hmmm ..
there is no backup ! :'(
ok thx for everything ... thx aloooooooooot
finalfantasy1st said:
Hmmm ..
there is no backup ! :'(
ok thx for everything ... thx aloooooooooot
Click to expand...
Click to collapse
Don't be an a$$. You did not make a back up before modding, so it is on you!
jimbridgman said:
Don't be an a$$. You did not make a back up before modding, so it is on you!
Click to expand...
Click to collapse
I took the CID backup via BMM in morning. Casually deleted it from SD. Deleted it via BMM in evening without taking backup. Trying to restore it using different undelete/data recovery tools from my SD. Not being successful still. Am I broke forever with my CID?
adnanschat said:
I took the CID backup via BMM in morning. Casually deleted it from SD. Deleted it via BMM in evening without taking backup. Trying to restore it using different undelete/data recovery tools from my SD. Not being successful still. Am I broke forever with my CID?
Click to expand...
Click to collapse
No, but you will have to get past it at every boot. You just go into the BPTools screen and find the boot normal, or something like that, option.
You will need to do that on every boot, if you do not have your CID anymore. The CID is generated special for each phone at manufacture time, so if you lose it somehow it is gone, and you will have to just bypass it at boot every time. There maybe some issues with certain apps that need it, but they should be few and far between.
jimbridgman said:
No, but you will have to get past it at every boot. You just go into the BPTools screen and find the boot normal, or something like that, option.
You will need to do that on every boot, if you do not have your CID anymore. The CID is generated special for each phone at manufacture time, so if you lose it somehow it is gone, and you will have to just bypass it at boot every time. There maybe some issues with certain apps that need it, but they should be few and far between.
Click to expand...
Click to collapse
Thanks for the reply jim. I want to know any good app using which I can recover my lost CID backup which I deleted casually from my SD.
Plus it would be great if you reply to my other serious concern here - http://forum.xda-developers.com/showpost.php?p=48940897&postcount=16
Thanks a ton.
adnanschat said:
Thanks for the reply jim. I want to know any good app using which I can recover my lost CID backup which I deleted casually from my SD.
Plus it would be great if you reply to my other serious concern here - http://forum.xda-developers.com/showpost.php?p=48940897&postcount=16
Thanks a ton.
Click to expand...
Click to collapse
Try something like this to undelete files, but you must be rooted.
https://play.google.com/store/apps/details?id=fahrbot.apps.undelete
Related
I wanted to flash to ARHD 6.3
This is my first time.. I managed to S off.. But then the bootloop began after I flashed PG58IMG.zip via fastboot.
Step 1. To S-OFF your Sensation - (You do not need to do this if you have S-off already or done this before) - WORKING NOW for TMOUS users
Visit
download the application for your operating System. AND EXTRACT IT TO A FOLDER
YOU MAY NEED TO DISABLE YOUR ANTIVIRUS PROGRAM- Norton is flagging up Revolutionary as a Virus when it isn't
IMPORTANT
Fill out the form under the download links with your OS, Device, Hboot Version and Serial number. This will give your beta key to enable you to S - OFF. Make a note of this.
How To get your Hboot Version - 3 methods below
1. [/url] and if it has found your device it should read
"Found your Device: HTC Sensation Z710* Applications -> Development)
4. With the phone switched on (not in HBOOT, just the regular home screen), plug in your USB cable and select HTC sync mode.(IGNORE any warning messages on your phone telling you it cannot find HTC Sync )
5. Launch revolutionary.exe. It should detect the phone and ask for your beta key. Type it (BE CAREFUL, as its case sensitive) or copy and paste it in.
If Revolutionary fails to find your phone verify you have all the drivers installed, try disk drive mode or charging mode (Linux users can use disk drive mode. Confirmed to be working by others)
6. Once you have entered your beta key correctly, follow any on screen prompts or actions from revolutionary and wait for it to S-Off,
7. You're done. Your Device will Successfully have S-OFF....if it hangs on method 3 and doesn't S-Off. See post 2 below for solutions.
IF REVOLUTIONARY SAYS FAILED YOUR PHONE IS NOT SUPPORTED. Go back and check hboot using the methods above. some users are told its failed and they still have S off now. If you have S-off your hboot will now be 1.17.1011 and revolutionary will tell you now your device is not supported
8. Revolutionary will now ask you to Install clockwork recovery mod after S OFF. Type N and install it manually below (the recovery provided is v4.0.1.4 doesn't charge when device is switched off, the one below v5.0.0.1 does charge)
9. Your Device now is S-off.
To install clockwork recovery for the sensation. Follow step 2!
STEP 2. To INSTALL Recovery - v5.0.0.8
1. Download recovery v5.0.0.8 for the Sensation HERE: or Multiupload
2. Copy the PG58IMG file into the Root folder of your SD card (The main Folder of your Memory Card)
3. Turn off your phone FUlly and reboot into the Bootloader/HBOOT screen (see post above on how to get to hboot screen)
4. Press Volume up to Accept when it asks" Do you want to start the update"
5. Press Power Off to Reboot back to android after installation is successful (normal screen with homescreen)
Click to expand...
Click to collapse
I got stuck at step 2.5.. Pls help me out. Actually I used to flash ROM for i9000 a couple of times but for sensation this is my first time. I'm using sensation unlocked. I lived in Malaysia so most probably its asians version.
ethanmars said:
I wanted to flash to ARHD 6.3
This is my first time.. I managed to S off.. But then the bootloop began after I flashed PG58IMG.zip via fastboot.
I got stuck at step 2.5.. Pls help me out. Actually I used to flash ROM for i9000 a couple of times but for sensation this is my first time. I'm using sensation unlocked. I lived in Malaysia so most probably its asians version.
Click to expand...
Click to collapse
Hi,
Try loading 5.0.2.0 HERE
Then follow THIS GUIDE to install 6.3.0
thank you so much for your reply!
i've downloaded that. Now how do i install it? fastboot only accept .zip files right? or is the instruction is in the 2nd link you gave me?
ethanmars said:
thank you so much for your reply!
i've downloaded that. Now how do i install it? fastboot only accept .zip files right? or is the instruction is in the 2nd link you gave me?
Click to expand...
Click to collapse
Hi,
Just rename 5.0.2.0 to PG58IMG.zip
Power off
Power on holding volume- and power button.
When it has finished,delete PG58IMG.zip
malybru said:
Hi,
Just rename 5.0.2.0 to PG58IMG.zip
Power off
Power on holding volume- and power button.
When it has finished,delete PG58IMG.zip
Click to expand...
Click to collapse
just pressed thanks, hehe..
i was wandering alone while waiting for your reply n managed to install ext4 touch recovery.. lol.. but still bootloop when pressed reboot.
now I wanna know will the 5.0.2.0 help me to access android again coz i haven't backup my contacts n sms yet..
let's say the answer is no, will it help if i make a nandroid backup now? or is it too late considering i cant access android anymore?
ethanmars said:
just pressed thanks, hehe..
i was wandering alone while waiting for your reply n managed to install ext4 touch recovery.. lol.. but still bootloop when pressed reboot.
now I wanna know will the 5.0.2.0 help me to access android again coz i haven't backup my contacts n sms yet..
let's say the answer is no, will it help if i make a nandroid backup now? or is it too late considering i cant access android anymore?
Click to expand...
Click to collapse
Hi,
Lesson for the future...
Always backup(nandroid,Titanium Backup,google) BEFORE starting anything major.
If you have 4EXT installed,then follow THIS GUIDE to install 6.3.0
malybru said:
Hi,
Lesson for the future...
Always backup(nandroid,Titanium Backup,google) BEFORE starting anything major.
If you have 4EXT installed,then follow THIS GUIDE to install 6.3.0
Click to expand...
Click to collapse
thanks again ..
so that means there's no way to access my phone like it was before eh?
btw, i thought it wasnt anything major coz it was just gaining an s off n then installing recovery.. then this happened.. i dont know what went wrong.. hmm
so i shall proceed with installing 6.3.0 since its like the only option i have left i believe?
ethanmars said:
thanks again ..
so that means there's no way to access my phone like it was before eh?
btw, i thought it wasnt anything major coz it was just gaining an s off n then installing recovery.. then this happened.. i dont know what went wrong.. hmm
so i shall proceed with installing 6.3.0 since its like the only option i have left i believe?
Click to expand...
Click to collapse
Hi,
Just as a matter of interest.
Do you still have a PG58IMG.zip on your sd card?
If so ,delete it.
Then it may boot into your ROM...
malybru said:
Hi,
Just as a matter of interest.
Do you still have a PG58IMG.zip on your sd card?
If so ,delete it.
Then it may boot into your ROM...
Click to expand...
Click to collapse
oh i've read that as well so i have deleted it manually by using sd adapter.. then reinserted it back n tried to boot normally.. but to no avail.. what's the root cause of this eh?
when i gained s off, i still can boot into my ROM.. however disaster happens when i flashed the .zip files obtained as per instructions..
oh but directly after i've flashed it, i didn't remove the .zip files n tried to immediately reboot into ROM.. does this make a difference?
ethanmars said:
oh i've read that as well so i have deleted it manually by using sd adapter.. then reinserted it back n tried to boot normally.. but to no avail.. what's the root cause of this eh?
when i gained s off, i still can boot into my ROM.. however disaster happens when i flashed the .zip files obtained as per instructions..
Click to expand...
Click to collapse
Hi,
Did you complete the s-off thread by rooting and getting SuperCID?
malybru said:
Hi,
Did you complete the s-off thread by rooting and getting SuperCID?
Click to expand...
Click to collapse
good question..
immediately after s off, i boot into my ROM and tried to install busybox and other apps that requires superuser or root but failed and stating that my device was still not rooted..
so i proceed to install a recovery (in this case its ext4 recovery) but failed to find a .zip installer (but managed to find the .apk and .img version but afraid to proceed considering the extension wasn't the same as per guide's PG5...ZIP). so i tried to simply install cwm as per stated in the guide. coz i know after recovery is installed, only then i would be able to install the su zip files.
then it boot looped.. n here we are trying to shoot all of these troubles.. XD
and if my understanding was wrong, pls correct me. thanks!
only after you sent me the links i managed to install ext4 recovery via a much easier method using cmd.exe..
n that also means that i wasn't even able to follow through the supercid part of the guide..
ethanmars said:
good question..
immediately after s off, i boot into my ROM and tried to install busybox and other apps that requires superuser or root but failed and stating that my device was still not rooted..
so i proceed to install a recovery (in this case its ext4 recovery) but failed to find a .zip installer (but managed to find the .apk and .img version but afraid to proceed considering the extension wasn't the same as per guide's PG5...ZIP). so i tried to simply install cwm as per stated in the guide. coz i know after recovery is installed, only then i would be able to install the su zip files.
then it boot looped.. n here we are trying to shoot all of these troubles.. XD
and if my understanding was wrong, pls correct me. thanks!
only after you sent me the links i managed to install ext4 recovery via a much easier method using cmd.exe..
Click to expand...
Click to collapse
Hi,
I follow THIS GUIDE
If you have 4EXT installed ,then you should be able to boot into recovery and make a nandroid,then root,then supercid...
malybru said:
Hi,
I follow THIS GUIDE
If you have 4EXT installed ,then you should be able to boot into recovery and make a nandroid,then root,then supercid...
Click to expand...
Click to collapse
wait a moment, i dont know if things are making more sense to me but, is it possible that this was caused by a wrong firmware? i just figured out my cid and its htc_044 and there are 4 different version of firmware for this cid, so should i try each of it until my phone boots to my original ROM?
Update: Oh God, I'm in such a relief! Thank God it works now. I flashed the firmware 1.17 n now am able to boot back into my ROM. Now i'm gonna get things backed up n will proceed. phew thanks so much for helping me out. The cause was maybe the zip files werent compatible with mine. So i check my cid n mid, n downloaded what might be the original one. so now its fixed..
I use official ICS, but I root my mobile and s-off. All works exelent. But I yesterday instal from google play ,,font instaler *root*,, and I check some font, click install, then reboot. Reboot cant be succeful. Stuck on htc logo. Now I just can open cwm recovery. I try wipe(all), factory reset, instal another custom rom, then I tried to instal RUU from hboot (I put PG88IMG.zip on sd card) loading succesful, but when he try to instal show for secund ,,PARSING.....PG88IMG.zip.... and back me on home hboot. Now when I try to on my phone After first htc logo show ,,black,,....no go... WHAT TO DO :crying: HELP ME PLEASE....
hboot 2.02.0002
Unlocked
S-ON
Are you using hboot 7.00?
teadrinker said:
Are you using hboot 7.00?
Click to expand...
Click to collapse
No, I use hboot 2.02.0002.
milosrdni94 said:
No, I use hboot 2.02.0002.
Click to expand...
Click to collapse
1) with this hboot you cannot be S-OFF (except with XTC Clip)
2) use the ICS RUU it should bring your phone back (but not as PG88IMG - just run the exe on your PC with a phone connected and in FASBOOT USB mode)
If the ICS RUU cannot restore your system you most probably have a faulty eMMC
amidabuddha said:
1) with this hboot you cannot be S-OFF (except with XTC Clip)
2) use the ICS RUU it should bring your phone back (but not as PG88IMG - just run the exe on your PC with a phone connected and in FASBOOT USB mode)
If the ICS RUU cannot restore your system you most probably have a faulty eMMC
Click to expand...
Click to collapse
1)I see wrong, is S-ON.
2) I try this, and on my pc show message ,, error conect,,. Maybe because dont turn on usb debuging?
here is app>>> https://play.google.com/store/apps/...SwxLDEsImNvbS5qcnVtbXkuZm9udC5pbnN0YWxsZXIiXQ.. read a worning mesage...
Connect to PC, reboot to bootloader and then select FASTBOOT with the volume buttons and press POWER button. You should see "FASTBOOT USB" written on the screen of the phone. Then run the ICS RUU
Sent from my HTC Desire S
I now try to instal ruu from PC. strart good, done some proces susceful, and when come ,,*something signature,, tu izbaci gresku. When I unplug usb on hboot show me message ,, ruu security faild,,..... What to do? Please help me.... Do something from CWM ?
You have to lock the bootloader as well:
fastboot oem lock
Sent from my HTC Desire S
amidabuddha said:
You have to lock the bootloader as well:
fastboot oem lock
Sent from my HTC Desire S
Click to expand...
Click to collapse
What you mean exactly? I dont understood what I to do now?
Can anyone help me? Please :crying:
This is a message from author of apk FONT INSTALER >>> Hey Lazar,
I sincerely apologize that your device is currently “soft bricked”. It’s never fun to have your device temporarily not working and I hope I can help you as best as possible.
When someone roots their device there is always a possibility of things going wrong. 99.9% of the time the device is easy to get back up and running. It does take some research to figure out exactly what needs to be done.
For this reason, our apps all include warnings of creating a nandroid backup before messing with the customization options.
When modifying system files a factory reset will not fix the device. This is because the factory reset wipes your data partition but your system is left untouched.
The easiest way to fix your device is to restore a “nandroid” backup in recovery. When a user roots his/her device a custom recovery, like clockworkmod recovery, is usually installed. In recovery you can create backups and restore your whole device to a previous state. If you created a nandroid backup and have a custom recovery please try to restore that backup in recovery. This will restore your system to a previous state and your device should be working again.
If you don’t have a nandroid backup but you do have a custom recovery you can install a ROM. There are many ROMs that can be found on xda-developers.com and rootzwiki.com. Installing a ROM in recovery will overwrite your system files and your device should then be working again.
If you don’t have a custom recovery installed then we are limited to our last option. Many manufacturers provide ways to restore the entire device. For devices made by Motorola this process involves using a “SBF” or “FXZ” and “RSD Lite”. Samsung uses “ODIN” and other devices may “fastboot flash” their device. I cannot provide great assistance here and your best option is to sign up on an Android forum and ask users who have your same device for help. I simply don’t know every process for every device and wish I could be more helpful. xda-developers.com and rootzwiki.com have many help forums and users willing to provide assistance. Also, usually if you just google “unbrick <your device>” then you can find a guide on how to fix your device.
Again, I apologize for the inconvenience and hope that the info I provided helps you out.
Can someone send me nandroid backup (ICS official wit htc sense) to try soft unbrick my desire s.
milosrdni94 said:
Can someone send me nandroid backup (ICS official wit htc sense) to try soft unbrick my desire s.
Click to expand...
Click to collapse
No!! What use would it be. Simply flash the ROM correctly. Read in the Stickies and Index thread, everything you need is in there.
Hi guys, a few day ago my One SV had some problems, rebooting itself and runs very slowly; so i tryed to do something like root it, but not knowing what i'm doing 'cause i don't have much time.
Probably installing a wrong rom, now I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags.
The phone stuck with htc logo, i only manage to go into bootloader, pdanet gives me sync error, twrp recovery doesn't work anymore.
Is there something I can do now?
VictorCic said:
Hi guys, a few day ago my One SV had some problems, rebooting itself and runs very slowly; so i tryed to do something like root it, but not knowing what i'm doing 'cause i don't have much time.
Probably installing a wrong rom, now I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags.
The phone stuck with htc logo, i only manage to go into bootloader, pdanet gives me sync error, twrp recovery doesn't work anymore.
Is there something I can do now?
Click to expand...
Click to collapse
As long as your device is Locked, you can't flash a custom recovery.
So unlock your device at htcdev.com, flash Twrp recovery and flash back a working rom.
Use a Android 4.1.2 rom, otherwise you will have problems with noisy sound.
old.splatterhand said:
As long as your device is Locked, you can't flash a custom recovery.
So unlock your device at htcdev.com, flash Twrp recovery and flash back a working rom.
Use a Android 4.1.2 rom, otherwise you will have problems with noisy sound.
Click to expand...
Click to collapse
Thanks, i've unlocked it and flashed Twrp recovery, but trying to using this last one always says unable to mount sd...
And could you help me to find the right rom or stock rom?
And trying to put it in s-off with revone, rumrunner, moonshine doensn't work
Thank you very much!
VictorCic said:
Thanks, i've unlocked it and flashed Twrp recovery, but trying to using this last one always says unable to mount sd...
And could you help me to find the right rom or stock rom?
And trying to put it in s-off with revone, rumrunner, moonshine doensn't work
Thank you very much!
Click to expand...
Click to collapse
How do you mount the sd?
At least pull it out of your device and put it into your PC and copy needed files in this way.
One thing i could not solve earlier (because of bad internet connection): did you already install the Android 4.2.2 update or what was your software running on your device before? Thats important to give you the right rom for your firmware!
I'll give you the links anyway:
4.1.2 -> http://forum.xda-developers.com/showthread.php?t=2254384
4.2.2 -> http://forum.xda-developers.com/showthread.php?t=2512742
Rumrunner & moonshine are confirmed working for your hboot, but which you should use at least also depends on your previous software.
old.splatterhand said:
How do you mount the sd?
At least pull it out of your device and put it into your PC and copy needed files in this way.
One thing i could not solve earlier (because of bad internet connection): did you already install the Android 4.2.2 update or what was your software running on your device before? Thats important to give you the right rom for your firmware!
I'll give you the links anyway:
4.1.2 -> http://forum.xda-developers.com/showthread.php?t=2254384
4.2.2 -> http://forum.xda-developers.com/showthread.php?t=2512742
Rumrunner & moonshine are confirmed working for your hboot, but which you should use at least also depends on your previous software.
Click to expand...
Click to collapse
Im sorry That error is from the twrp recovery when i try to install superuser.. It says unable to mount int sd.. I think internal memory
Ignore it. Only use the files, recommended in my index thread (use SuperSu, not Superuser), link in my signature.
And answer the other question.
old.splatterhand said:
Ignore it. Only use the files, recommended in my index thread (use SuperSu, not Superuser), link in my signature.
And answer the other question.
Click to expand...
Click to collapse
Sorry i had update it to 4.2.2
Ok, so you can use the second link for the stock rom. And rumrunner for S-off.
old.splatterhand said:
Ok, so you can use the second link for the stock rom. And rumrunner for S-off.
Click to expand...
Click to collapse
I installed the 4.2.2 versions, seems completed but phone remains with black screen showing only the top bar with the clock, then reboot itself; sometimes after reboot it shows the bottom clock and lock, you can also unlock it, but then it reboots;
One time it shows me the backgroud.
Maybe it's a motherboard problem, what do you think?
Thanks
VictorCic said:
I installed the 4.2.2 versions, seems completed but phone remains with black screen showing only the top bar with the clock, then reboot itself; sometimes after reboot it shows the bottom clock and lock, you can also unlock it, but then it reboots;
One time it shows me the backgroud.
Maybe it's a motherboard problem, what do you think?
Thanks
Click to expand...
Click to collapse
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
old.splatterhand said:
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
Click to expand...
Click to collapse
Yes, flashed boot.img and wipe data/cache/dalvik.
Later i'm gonna try the 4.1.2.. I hope that will work
VictorCic said:
Yes, flashed boot.img and wipe data/cache/dalvik.
Later i'm gonna try the 4.1.2.. I hope that will work
Click to expand...
Click to collapse
old.splatterhand said:
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
Click to expand...
Click to collapse
installed the 4.1.2 version..same as before (black screen, only the first time turned on it showed the background), apart it can show every time the ring to unlock the screen; unlocking it it reboot itself...
VictorCic said:
installed the 4.1.2 version..same as before (black screen, only the first time turned on it showed the background), apart it can show every time the ring to unlock the screen; unlocking it it reboot itself...
Click to expand...
Click to collapse
Stop. Did you only wipe data/cache/dalvik.
No system?
You need to wipe all, except internal & external sd!
old.splatterhand said:
Stop. Did you only wipe data/cache/dalvik.
No system?
You need to wipe all, except internal & external sd!
Click to expand...
Click to collapse
Also system yes. And if i wiped the internal sd?
anyway after installing the rom, from twrp internal storage is 0 MB
Then i'm running out of ideas
As the roms worked for other people, i also start thinking thats something bugged with your device.
You checked md5sum of the roms? Using latest TWRP recovery?
old.splatterhand said:
Then i'm running out of ideas
As the roms worked for other people, i also start thinking thats something bugged with your device.
You checked md5sum of the roms? Using latest TWRP recovery?
Click to expand...
Click to collapse
Yes, used the latest TWRP recovery.
the recovery say to me no md5 file, is this the problem?
How can I check the md5 now?
I don't know the name of the tool (i'm at work), but you will find it with google search, i think.
In recovery this is not a problem, its only to check on your pc, if the downloaded file is the same as the upload.
old.splatterhand said:
I don't know the name of the tool (i'm at work), but you will find it with google search, i think.
In recovery this is not a problem, its only to check on your pc, if the downloaded file is the same as the upload.
Click to expand...
Click to collapse
Checked, the codes matches..
Then i think your device has a defect
old.splatterhand said:
Then i think your device has a defect
Click to expand...
Click to collapse
Hi, i managed to change the motherboard, so trying to put a mod, the phone now stuck on the htc logo...
I unlocked it with htcdev, then installed the recovery but this one doesn't work, it says starting recovery but doesn't start..(trying to install a different recovery, it seems unable to rewrite it)
trying to do something i flashed with fastboot the stock boot.img and now the phone doesn't start anymore..
what can i do now? :crying:
After flashing sense rom (walkman sense) pico freezes and automatically restarting.. :crying:
Tried flashing super_wipe.zip before flashing rom, and tried other roms too (cm11,carbon,nextgen,jaggy..!! ). The problem still persist..
How to fix this..??
Pee_kee said:
After flashing sense rom (walkman sense) pico freezes and automatically restarting.. :crying:
Tried flashing super_wipe.zip before flashing rom, and tried other roms too (cm11,carbon,nextgen,jaggy..!! ). The problem still persist..
How to fix this..??
Click to expand...
Click to collapse
some questions/ info needed
What recovery you using at the moment
Did you format everything but sdcard
Which firmware are you on / which region
anonymous-user said:
some questions/ info needed
What recovery you using at the moment
Did you format everything but sdcard
Which firmware are you on / which region
Click to expand...
Click to collapse
recovery : Latest TWRP
formatted every thing.. flashed superwipe.zip
am in india using Walkman sense rom 5.10.
problem persist in all rom..
Pee_kee said:
recovery : Latest TWRP
formatted every thing.. flashed superwipe.zip
am in india using Walkman sense rom 5.10.
problem persist in all rom..
Click to expand...
Click to collapse
ok, well have you tried relocking your bootloader and flashing RUU package back to full clean stock? if you`ve already done that properly (not by flashing some custom stock rom through recovery) then I guess its a repair shop job.
anonymous-user said:
ok, well have you tried relocking your bootloader and flashing RUU package back to full clean stock? if you`ve already done that properly (not by flashing some custom stock rom through recovery) then I guess its a repair shop job.
Click to expand...
Click to collapse
I didn't do that /*relocking your bootloader and flashing RUU package*/..
well, let me seek tutorials to do that.
Any tutorial with less risk than this one.? http://forum.xda-developers.com/showthread.php?t=1500165
Pee_kee said:
Any tutorial with less risk than this one.? http://forum.xda-developers.com/showthread.php?t=1500165
Click to expand...
Click to collapse
1st you need to find your firmware version, boot into bootloader and the info is there and then download the appropriate RUU package as these are region specific, I can tell you how to do it without much hassle so long as you have adb setup on your comp already and the unlock token or application used to unlock your bootloader.......
you can find all the RUU packages for pico here : http://www.androidruu.com/?developer=Pico
tell me which 1 it is and I`ll extract the files needed to be able to update it via sdcard
anonymous-user said:
1st you need to find your firmware version, boot into bootloader and the info is there and then download the appropriate RUU package as these are region specific, I can tell you how to do it without much hassle so long as you have adb setup on your comp already and the unlock token or application used to unlock your bootloader.......
you can find all the RUU packages for pico here : http://www.androidruu.com/?developer=Pico
tell me which 1 it is and I`ll extract the files needed to be able to update it via sdcard
Click to expand...
Click to collapse
This is RUU_Pico_hTC_Asia_India_1.31.720.3_Radio_10.35d.80.09H_1.11.82.17_release_230683_signed.exe
Pee_kee said:
This is RUU_Pico_hTC_Asia_India_1.31.720.3_Radio_10.35d.80.09H_1.11.82.17_release_230683_signed.exe
Click to expand...
Click to collapse
ok I have the specific RUU package for your region downloaded and I`ve extracted the rom.zip from the package, now I`m in the process of uploading the file for you. So you have adb working? the unlock token you used to unlock your bootloader or utility that will do the same job?
Ok here`s the full procedure for you
Download the the full firmware stock rom from here: http://www.freefilehosting.net/pj03img press "DOWNLAD THIS FILE" then enter the captcha, the file name is "PJ03IMG" do not modify it in anyway.
Copy the PJ03IMG file to the root of your sdcard (not in any folder)
Boot to Bootloader and connect usb to phone and computer, open CMD on windows or Terminal on Linux and type the following:
Code:
fastboot oem lock
you should now see on the phone that your bootloader has been "re-locked" if you see that you can now press the power button on phone to change to bootloader (mode see attached pic 1 at the bottom), now the phone will look for files on your sdcard (see pic 2 attached at the bottom)
at this point it should find the PJ03IMG file and a loading bar will appear on the right hand side, be patient it takes about 30 secs to load it. When its finished it will ask if you want to flash the update or not, use the volume keys to move the selector to yes and press the power button and the process will begin to totally reflash your phone back to stock once done it will ask you to reboot phone, voila done. the first boot will take some time as its a fresh install so give it afew minutes to get to homescreen, assuming all is well and phone is working as it should we can get a recovery back after unlocking the bootloader.
anonymous-user said:
will ask if you want to flash the update or not, use the volume keys to move the selector to yes and press the power button and the process will begin to totally reflash your phone back to stock
Click to expand...
Click to collapse
how pico do that without stock rom file.?! Where i should should keep rom.zip file.? how can i extract it from RUU_Pico_hTC_Asia_India_1.31.720.3_Radio_10.35d.80 .09H_1.11.82.17_release_230683_signed.exe..??
Is it possible my phone to hard brick or soft brick itself while i use it with a custom rom? I got this phone 3 weeks ago and if i break it, no smartphone for me for years (very tight budget).
geniiii said:
Is it possible my phone to hard brick or soft brick itself while i use it with a custom rom? I got this phone 3 weeks ago and if i break it, no smartphone for me for years (very tight budget).
Click to expand...
Click to collapse
Most cases a custom recovery for your phone will not do any harm
But before flashing read posts carefully because I soft bricked my phone because of a buggy twrp build
sjandroiddeveloper said:
Most cases a custom recovery for your phone will not do any harm
But before flashing read posts carefully because I soft bricked my phone because of a buggy twrp build
Click to expand...
Click to collapse
I meant a custom rom, i want to use FlexOS but i am kinda worried that it could brick my device while i use it. Is that possible?
I am already using a custom recovery, supersu and xposed alpha 3.
geniiii said:
I meant a custom rom, i want to use FlexOS but i am kinda worried that it could brick my device while i use it. Is that possible?
I am already using a custom recovery, supersu and xposed alpha 3.
Click to expand...
Click to collapse
No it will not brick
But you must first have enough info of what you are doing
sjandroiddeveloper said:
No it will not brick
But you must first have enough info of what you are doing
Click to expand...
Click to collapse
Thanks!
Sorry to hijack, but it's kind of related. Are there consequences to flashing the incorrect regional stock ROM?
Blkdrgn415 said:
Sorry to hijack, but it's kind of related. Are there consequences to flashing the incorrect regional stock ROM?
Click to expand...
Click to collapse
No just keep in mind the model like xt1033 or xt1032
sjandroiddeveloper said:
No just keep in mind the model like xt1033 or xt1032
Click to expand...
Click to collapse
Just to be clear, mines is a XT1039 with a CID of 7. My build number is also ""KXB21.14-L1.56" which is exactly matches with Germany where as every other one with CID7 ends with "-1", can I also use the other regions or do I need to use Germany. What are also the differences between the regions?
Blkdrgn415 said:
Just to be clear, mines is a XT1039 with a CID of 7. My build number is also ""KXB21.14-L1.56" which is exactly matches with Germany where as every other one with CID7 ends with "-1", can I also use the other regions or do I need to use Germany. What are also the differences between the regions?
Click to expand...
Click to collapse
The basic thing is you can flash different region firmwares for the same specific device like xt0139 in you case as I was able to flash both Asian and Brazilian firmware in my xt1033
The difference in the firmwares in region specific apps and different radios
sjandroiddeveloper said:
The basic thing is you can flash different region firmwares for the same specific device like xt0139 in you case as I was able to flash both Asian and Brazilian firmware in my xt1033
The difference in the firmwares in region specific apps and different radios
Click to expand...
Click to collapse
Thanks for the help, one last thing though. What if I made a recovery via CWM to my internal SD, but moved it to my external SD, would the recovery still work, and are there any risks of flashing a recovery that is incomplete as whenever I use Recovery Manager to backup to my external SD, it always hangs at "Generating md5 sum" and I'm forced to manually restart.
Blkdrgn415 said:
Thanks for the help, one last thing though. What if I made a recovery via CWM to my internal SD, but moved it to my external SD, would the recovery still work, and are there any risks of flashing a recovery that is incomplete as whenever I use Recovery Manager to backup to my external SD, it always hangs at "Generating md5 sum" and I'm forced to manually restart.
Click to expand...
Click to collapse
By recovery do you mean backup
And press thanks instead of saying
sjandroiddeveloper said:
By recovery do you mean backup
And press thanks instead of saying
Click to expand...
Click to collapse
I think so. Whatever CWM calls it's backups.
Blkdrgn415 said:
I think so. Whatever CWM calls it's backups.
Click to expand...
Click to collapse
Recovery means the software that can perform tasks like flashing wiping or backing up
And its always called backups and not recovery be it cwm or twrp
Blkdrgn415 said:
Thanks for the help, one last thing though. What if I made a recovery via CWM to my internal SD, but moved it to my external SD, would the recovery still work, and are there any risks of flashing a recovery that is incomplete as whenever I use Recovery Manager to backup to my external SD, it always hangs at "Generating md5 sum" and I'm forced to manually restart.
Click to expand...
Click to collapse
Yes you can made backup in internal memory and move it to external memory or even to other storage devices or to your computer. If you want to restore the backup again, put the backup in concerned folder in your mobile and restore it from recovery :good:
sjandroiddeveloper said:
Recovery means the software that can perform tasks like flashing wiping or backing up
And its always called backups and not recovery be it cwm or twrp
Click to expand...
Click to collapse
Mr Y said:
Yes you can made backup in internal memory and move it to external memory or even to other storage devices or to your computer. If you want to restore the backup again, put the backup in concerned folder in your mobile and restore it from recovery :good:
Click to expand...
Click to collapse
So is there any threat to restoring a backup that may be corrupted or incomplete since I manually restarted when it hung up at "Generating md5 sum..."?
Also, will using these files completely restore my phone back to when I first got it? For example, if a crucial system file was corrupted, would using these files fix it, or if my phone has been soft bricked, would it fix it?
http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619
+thanks
Blkdrgn415 said:
So is there any threat to restoring a backup that may be corrupted or incomplete since I manually restarted when it hung up at "Generating md5 sum..."?
Also, will using these files completely restore my phone back to when I first got it? For example, if a crucial system file was corrupted, would using these files fix it, or if my phone has been soft bricked, would it fix it?
http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619
+thanks
Click to expand...
Click to collapse
1. If the backup you made previously was corrupted or incomplete, then the recovery wont start the process of restoring.
2. Yes. It will fix the soft-bricks and the phone will be restored to its "Out of box" state except your bootloader will still be in unlocked state since there is no syntax to lock your bootloader in the given link.
Mr Y said:
1. If the backup you made previously was corrupted or incomplete, then the recovery wont start the process of restoring.
2. Yes. It will fix the soft-bricks and the phone will be restored to its "Out of box" state except your bootloader will still be in unlocked state since there is no syntax to lock your bootloader in the given link.
Click to expand...
Click to collapse
Thank you so much, I've been contemplating whether to use my recovery and the stock firmware for weeks.
+thanks
Blkdrgn415 said:
Thank you so much, I've been contemplating whether to use my recovery and the stock firmware for weeks.
+thanks
Click to expand...
Click to collapse
I'll advise you to keep stock firmware as safety measurements (if something goes wrong) and explore other ROMs and tweaks.:good:
Mr Y said:
I'll advise you to keep stock firmware as safety measurements (if something goes wrong) and explore other ROMs and tweaks.:good:
Click to expand...
Click to collapse
Will do, I'm new to phones in general, do you have any recommendations on popular ROMs for my Moto G 4G/LTE XT1039 KitKat 4.4.4?
Official CM 11 are stable in my opinion. Resurrection Remix ROMs also doig great job. BTW im CM fanboy. So better test yourself to choose wisely.