Flash via SD - Why does it have to be blank? - 8525, TyTN, MDA Vario II, JasJam General

Any reason why the HERMIMG.nbh file has to be on a blank SD card? Can it be in the root of the card and still have folders on it? Anyone know why not if so? Would be handy to have all the ROM's in their own folder and move it to the root when you need it.
Thanks...

Or even better to have a bootloader which provided you with an option on which ROM/IMAGE to load...

It doesn't have to be blank, I have just been leaving the root empty, and all other files except hermimg in folders/directories, have flashed countless times in this manner, with no problems.
And yes you can have a selection of radio's and os's ready to go, just don't leave them in the root.
I also suspect the root doesn't have to be empty also..the bootloader is just looking for hermimg.nbh I figure, but I never pushed my luck, and I don't advise it, incase someone jacks their device up trying it.

ChaoticDruid said:
It doesn't have to be blank, I have just been leaving the root empty, and all other files except hermimg in folders/directories, have flashed countless times in this manner, with no problems.
And yes you can have a selection of radio's and os's ready to go, just don't leave them in the root.
I also suspect the root doesn't have to be empty also..the bootloader is just looking for hermimg.nbh I figure, but I never pushed my luck, and I don't advise it, incase someone jacks their device up trying it.
Click to expand...
Click to collapse
Ah, ok... it was just from reading the wiki that said it had to be blank. Thanks for the info!

I left my SD card as-is to see what would happen. Subdirectories and files aplenty.
No issues what-so-ever flashing.

Related

Siemens SX-56 Dead Dead Dead!

ok...I'm really new to all this so please show a little patience towards me!
I was trying to load the XDA-developers-SER-v12 on my phone and just when it started with the progress bar moving at the top of the PPC screen, when it said "Do not Remove Device..." I accidently lifted the phone out of the cradle as dumb as I am...! After that I tried to hard start it by shoving a pin on the hole in the right side under the battery icon with the cross (hard-reset) and got the Bootloader 5.17 screen with the three colors and GSM (OK) there when I pressed the soft-reset and power buttons simultaneously.
But since I was the idiot and could not understand what was going on, as I was not in this forum nor even behind a computer, I reset it again and again a couple of more times. Now present situation; I have the same "Do not Remove..." screen everytime I do a hard or soft reset even if I keep the power on/off button pressed alongwith pressing the hot or cold boot buttons on the left and right corners respectively. In fact the screen has gotten badly distorted but the same "Do not Remove..." comes up in the totally distorted state on the screen and the Bootloader or the colors, nothing comes up anymore.
When I try to put the phone on the charger, the light goes orange just as if it is charging, in fact, after an hour or so, just as it normally would in the correct phone state, it turns green.
Is my phone toast or can I still do something about it?
Munz.
I'm no expert, but it seems to me that if there is a complication with the software when loading, one should try using the sd method of rom flashign. Cook or dl a rom, use XDA tools to load it to an SD, put the SD into the device, and then use the bootloader to load off of SD. Other than that, I know little to nothing.
Good luck!
Search in the forum after SD Card flashing for the Wallaby.
This would fix your device...
HTH
Stefan
Re: Dead SX-56
You guys are good and quick....but!!! As I mentioned, I can't even see the Bootloader even after a reset and power button combo...nothing comes up or happens...the screen just blinks and then goes blank...should I open it up and disconnect the battery or something...? Right now I am just seeing the screen saying "Do not Remove...." and that even in a totally distorted form....
Try pushing a pin in the hard reset, push once only, leave it overnight, I think that is good as removing battery as it disconnects the connection between battery and mainboard as fas as I know. Next morning push once with oin again, you never know your luck. Its weird that the bootloader should be affected however the good thing is that your gsm seems ok and the xda is charging.
XDA Dead!
Thanks for the reply...I have just pushed the pin and am leaving the XDA in that state for the whole day...hope it revives back...its presently just giving me a garbled screen and nothing else...even when I press the power and hard reset together, it comes back to the garbled screen and nothing else...I'll take your advice and not touch it after the above for the day and let you know what happens, if there is any other advice I would highly appreciate it...
Bootloader Malfunction
You mentioned that your bootloader seems to be screwed up. Download the full version of XDA tools WITH the bootloader and Programme A. Grab yourself a new ROM of your choosing, lumpistefan's kitchen, etc. Then use the XDA tools to write the bootloader and the rom to your SD card. After that hard booting the device with the SD card installed should ask you if you want to flash the device.
I noticed that if you have XDA tools without the bootloader file it will write the rom to your SD and you will NOT be able to get to the flash your device screen.
This is the only way to do it since your device will not boot to a rom. Upgrades from manufactures and roms prepared with Programme A all require MS Active Synch AND a good working connection.
If you have a SD card prepared with the ROM and the bootloader the right way, it should almost be foolproof from what I understand.
Hope this helps, I was in much the same situation
XDA Dead!
Yups! I tried to boot it from an SD Card, its not exactly an SD Card but an MMC Card (128MB). It still comes up to the same garbled screen which is more garbled than ever before! Does not ask me for anything; or even confirms anything...It does not do anything else besides the screen even after a soft reset/hard reset or a combo hard/soft power button reset.
I'm really totally stuck...Any ideas will be much appreciated!
Thanks.
Your XDA is completely dead; you screwed OS ROM and bootloader.
Forget SD or Details method, it won't work for you!
Re: Dead SX-56
Can you help me fix it please? What do I need to do?
Bootloader
The more experienced members of this forum can correct me on this, but I have been under the impression that the SD method of flashing does not require an intact OS ROM or bootloader on the device.
If you created the SD correctly, it should contain its own bootloader. Just putting it in the unit and then reseting it should come up with the screen to flash the device.
Did you create the SD card with XDAtools? Did you also have the bootloader file in the /bin directory when you did it?
If a properly created SD "flash" card cannot fix your problem, then you really might have no choice to but to get it professionally repaired where the remove the chips themselves and replace them.
I think you may even be in luck. www.pocketpctechs.com probably can do this and they are located in Fountain Valley, CA about 4 hours away from you. They can also put in bigger memory and batteries at the same time at a discount if you are getting it repaired
Re:
Thank you so much for the reply...I will try it once more; although, yes I have tried the same thing before and made the MMC Card through the XDATools, but never hurts to try again...I'll double check on the bootloader again too this time...
If you can, please send me the contact information for the people who fix the XDA's professionally as you mentioned in the USA somewhere near me preferably, I am in San Jose, CA...I'll try to contact them also...
Best Regards.
Contact Information
Their website is www.pocketpctechs.com.
You can find all the contact information right there. As far as I know fountain valley is about 4-5 hours away from San Jose.
Similar problem:
I have a XDA I here, which has a similar problem:
It boots with the welcome to T-Mobile screen, and
it shows at the bottom of the screen 4.01.16 after a while R4.06 and after a while G32S54. The machine locks-up and does not respond to anything except the touch screen. If i tap the screen, the backlight turns on, and a
rotating 'wait' icon appears. That's it. I am not able to put it in Bootloader mode by pressing power - > reset, so i cannot reflash the unit using SD.
I guess the former user has tried to reflash the unit, and had put the OS overwriting the bootloader, OTOH, the unit seems to run *some* code, since it responds to taps on the screen, by turning on the backlight.
Any guru have any clue on this one? I could not find anything in the forums, while the forums are VERY helpful in the past.
GreetingZ,
Richard
Bootloader
<<I am not able to put it in Bootloader mode by pressing power - > reset, so i cannot reflash the unit using SD>>
I really do not understand that. I am not a Guru by any means, and I hope one does make a comment on this.
As far as a I can tell by my own experiences, you do not need to put it in Bootloader mode by presseing power-reset. That is totally unneccessary to flash the unit. In fact, in Bootloader mode I have never found any command or method to flash the unit from the sd card. Only methods to backup the rom to the sd card. So I am really really confused to hear you guys say that.
I have successfully flashed XDA's with 2 methods. Programme A by which the XDA is connected to Active Synch 3.7 and by an SD card created by XDAtools.
Programme A only seems to work when there are NO problems at all and you just want to upgrade or try something else.
The SD card method seems to be the choice for repair.
Creating the SD card with XDAtools *WITH* the bootloader file in the /bin directory does work. The SD card I created with this method DID not, i repeat, DID not need the Bootloader (power-reset). It only needed to be powered on with the SD Card in the XDA.
If there are any Gurus moderating this post, I would sincerely appreciate having this cleared up
Re: Bootloader
ed207_us said:
<<I am not able to put it in Bootloader mode by pressing power - > reset, so i cannot reflash the unit using SD>>
I really do not understand that. I am not a Guru by any means, and I hope one does make a comment on this.
Click to expand...
Click to collapse
I also have a good working unit, and testing my SD card, created with XDARIT in this unit tells me i need to press power -> reset to be able to
flash the unit. if i do'nt hold the power button, the unit boots normally.
ed207_us said:
As far as a I can tell by my own experiences, you do not need to put it in Bootloader mode by presseing power-reset. That is totally unneccessary to flash the unit. In fact, in Bootloader mode I have never found any command or method to flash the unit from the sd card.
Click to expand...
Click to collapse
It is there. 'press action to download ROM, or press record to exit'
ed207_us said:
<<
Only methods to backup the rom to the sd card. So I am really really confused to hear you guys say that.
I have successfully flashed XDA's with 2 methods. Programme A by which the XDA is connected to Active Synch 3.7 and by an SD card created by XDAtools.
Click to expand...
Click to collapse
I cannot connect the unit to activesync.
ed207_us said:
<<
Programme A only seems to work when there are NO problems at all and you just want to upgrade or try something else.
The SD card method seems to be the choice for repair.
Creating the SD card with XDAtools *WITH* the bootloader file in the /bin directory does work. The SD card I created with this method DID not, i repeat, DID not need the Bootloader (power-reset). It only needed to be powered on with the SD Card in the XDA.
Click to expand...
Click to collapse
I don' know the contents of the SD, since i created it a long time ago, but i really would appreciate is if you can email me a image of yours. Hope you are right and i can use the bootloader on your card to start this unit.
email size is no problem upto 100Mb
ed207_us said:
<<
If there are any Gurus moderating this post, I would sincerely appreciate having this cleared up
Click to expand...
Click to collapse
<<ed207_us wrote:
As far as a I can tell by my own experiences, you do not need to put it in Bootloader mode by presseing power-reset. That is totally unneccessary to flash the unit. In fact, in Bootloader mode I have never found any command or method to flash the unit from the sd card. >>
<<<RichardRosenberger wrote:
It is there. 'press action to download ROM, or press record to exit' >>>
It is only there when you have the SD card in the device, otherwise you cannot find it by moving around through the different menus.
XDAArit is completely outdated. You need to get their new tool.
XDATools can be downloaded from the website here. The best thread that talks about the tool is:
http://forum.xda-developers.com/viewtopic.php?t=2189&highlight=xdatools
The exact link to get the tool and all the supporting files, including the bootloader is:
http://cuba.calyx.nl/~jsummers/XDA/XDAtools-Jeff.exe
When you install this version of XDAtools you will find a directory called binaries. Under it there should be a file called "bootloader_v5_15.nb0"
Use the tool to create your SD card with a .nb1 file of your choice. After that it should only be a matter of powering on the device with the SD card inside the unit.
I have 2 XDAs. 1 good en 1 have problem with bootloader and rom.
I can't access Wallaby bootloader en the OS don't start.
I backup it from good XDA in the bootloader (ce+Boot) and i pushed my SD in the XDA where problems are..
He don't work. How can I fix my problem..
Please Help...
I am not aware of what the (ce+boot) actually creates on the SD card. If that is the exact ROM that you want, I would suggest downloading the full version of XDA tools, and I think you can use it to copy the ROM from the SD card to a .nb1 file on your computer. Then follow the instructions I have already posted to make the working SD card that will flash the XDA.
When it comes to the SD card, the only time I have ever been successfull is when creating it with XDAtools with a .nb1 file and the bootloader .nb0 file inside the binaries directory.
That's it. I have never been able to do it any other way. Programme A does not count since it requires an active and working OS and connection to the PC and most people that are in trouble don't have that.

where did it go?

So I downloaded some ringtones from myxer.com they show up and play through the settings fine. But I can't find the actual files themselves. I've looked in the sd download area. And internal media file and the stock ringtone file. Does anyone know where it would be?
how did you 'download' them? browser? mms?
I just looked, looks like through MMS. What ROM are you using? If you have cupcake, just open the message that you got the file from and save to the SD card, and it will be in the download area. If you don't have a cupcake ROM, then you are missing out on some features.
I'm using haykuros apd 1.5hr3 rom. I downloaded it through the browser. I'm a little new but I know the basics and some advanced since I've bricked my phone repetedly time and time again through trial and error . But I just can't seem to find it. Someone should try to download a ringtone from myxer.com dirctly from the g1 and let me know if u can find it
I see what you mean dude, I'm trying to find it now too.
Hmm.... Usually if you download anything it ends up in the Downloads folder. Next time make a copy of it or move it to your SD Card if you can.
Also the technical term of "bricking" means the device has rendered itself useless (no boot, no recovery etc, won't turn on at all), effectively turning it into a paperweight, like a brick ^_- Most likely you've meant that the device has "boot looped" instead.
I only say this because people are not using the terms correctly, confusing others. Its like people on Windows saying they've got a "virus" when a program crashes... Most likely that isn't the case.
NeoBlade said:
Hmm.... Usually if you download anything it ends up in the Downloads folder. Next time make a copy of it or move it to your SD Card if you can.
Also the technical term of "bricking" means the device has rendered itself useless (no boot, no recovery etc, won't turn on at all), effectively turning it into a paperweight, like a brick ^_- Most likely you've meant that the device has "boot looped" instead.
I only say this because people are not using the terms correctly, confusing others. Its like people on Windows saying they've got a "virus" when a program crashes... Most likely that isn't the case.
Click to expand...
Click to collapse
Gotchya. Not bricking then. Infinate loop. Regardless, I've downloaded programs and roms dirctly from my g1 and using 2 sd cards flashed and etc. But this specifically doesn't go to the download folder

Cant boot anymore

Hi folks, i'm looking for 2 days a way to solve my DHD problem:
It can't boot anymore. It pop up the "htc quietly brilliant" screen, play the boot sound and, start this step again, and again, and again...
So I'm googling a LOT about how to solve this, if exist a way to restore the original rom. Because i'm thinking that was the problem, my original rom is gone.
That happens when i try to install 3 softwares from appbrain, my device got freeze and i hit the power button to reset. So, after that, my device is gone.
So i came here, to ask you folks: There is a way to recover the original rom ? Without send to warranty (because it spend something like 1 month here).
I'm not a mobile hacker or something, i'm just trying to be happy with my device.
Thanks a lot and sorry for my poor english!!
Perhaps try booting to the bootloader, by holding Power + Volume down button. From there, you should be able to do a factory reset, which may or may not fix your problem. Worth a shot at least, imo
And if it does not work when you do a factory reset, you can use a rom.zip from HTC RUU to restore your phone.
Now the important thing is to know which HTC rom you are running. If it is unbranded, 1.72.405.3 is a sure shot. Download the RUU.exe from Stock roms thread in android development subforum, and run it. When the window pops up, open run prompt, and type: "%TEMP%". Then search for rom.zip, copy it to your desktop, rename it to PD98IMG.zip and put it to your SD card (I hope that you have a card reader). Then just reboot to bootloader as tmh described, and watch the magic happen
Then if your phone is branded, you can still use the same technique to make PD98IMG.zip, but you have to get the RUU that matches your branding. There are lots of RUUs in android development subforum, just search.
Hi guys,
thanks a lot for quik reply!
I perform the procedure indicated by tmh, but without lucky ;\
I think it is unbranded. I buy it at Portugal and i'm using at Brazil right now.
I'll perform your tip jkoljo.
I'll post a repply to let people know if it works or not.
Thanks a lot!!
Hope the advice the last guy gave helps , a factory re set may work fine and fix the issue. Iv had 3 dhd since the day of release , the second one I had wouldn't switch on, had it replaced by Vodafone . Not sure weather or not they will give you a new one . Hope u get it fixed
Sent from my Desire HD using XDA App
I'm not sure if i got cover from warranty.
Right now, my "PROOF OF PURCHASE" is at europe, and i'm at america, so i must get this work again by myself, or pay (some expensive value, i think) for htc support.
I found those ROM version:
RUU_Ace_HTC_WWE_1.72.405.3_R2_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_163262_signed.exe 04-Jan-2011 12:41 285M Windows executable file
RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_26.04.02.17_M2_release_161342_signed.exe
but i'm not sure about "WWE". What it means?
dogasantos said:
I'm not sure if i got cover from warranty.
Right now, my "PROOF OF PURCHASE" is at europe, and i'm at america, so i must get this work again by myself, or pay (some expensive value, i think) for htc support.
I found those ROM version:
RUU_Ace_HTC_WWE_1.72.405.3_R2_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_163262_signed.exe 04-Jan-2011 12:41 285M Windows executable file
RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_26.04.02.17_M2_release_161342_signed.exe
but i'm not sure about "WWE". What it means?
Click to expand...
Click to collapse
the different is just the radio version. just try flash one of them and see if that work.
WWE means World Wide English, which is an international release
Any one of those RUUs you linked is ok, as hedayat7 already said.
WWE is World wide English...so both are english Roms...try the RUU flash, it should work like a dream....
jkoljo said:
Download the RUU.exe from Stock roms thread in android development subforum, and run it.
Click to expand...
Click to collapse
Sorry ask for your help again, but at Official thread (thread number 841207) for DHD files, both 1.72.405.3 links are broken.
So i search for another thread, and found another one, but when i run the .exe, it ask for a USB connection to device, so it appears wrong.
Could you gimme a hand to find the correct file?
PS: I can help with a web hosting to all correct files.
You probably found the correct RUU, now proceed to %TEMP% and copy rom.zip to desktop.
You can find RUUs here: http://xdafil.es/index.php?path=DesireHD/RUU/
I am not completely sure if those zip files are actual rom.zips, you can check that. Open up the zip, and if it has a long list of hboot, system, android-info.txt etc, then it is rom.zip and you can just go ahead and rename it to PD98IMG.zip.
jkoljo said:
You probably found the correct RUU, now proceed to %TEMP% and copy rom.zip to desktop.
You can find RUUs here: ...
I am not completely sure if those zip files are actual rom.zips, you can check that. Open up the zip, and if it has a long list of hboot, system, android-info.txt etc, then it is rom.zip and you can just go ahead and rename it to PD98IMG.zip.
Click to expand...
Click to collapse
But i did that.
The "1.72.405.3" files at this URL are broken (Or need password to access it, because "You don't have permission to access" message pop up).
When i run the RRU i got two screens, first i must accept a advice, the second one ask if I have a USB connection to my device. Even when i proceed to next step, i got no .zip file on my %TEMP%.
Im lost because of that lol
UPDATE: OK I FOUND IT! haha ty
Thanks a lot my friends,
but it doesn't work.
I perform the process for 2 different roms, and it doesn't work.
Still can't boot.
I'll sent for warranty and wait a loooong time..
But thanks a lot for help me with this!!
Ok, then there is something wrong in the device itself. You have to send it to a service center.
Sent from my Desire HD using Tapatalk
Hi again,
i keep a little hope that i can restore my phone, so i found a possible solution:
OTA update.
At "showthread.php?t=667728&page=2", i found a guy with the same problem i think, here is the quote:
Kinma said:
I had the same problem last week.
I suspected it had to do with the EXT3 partition.
Solved it by first flashing the OTA 2.2 ROM (for rooted users) as this does not use the EXT3. Then used Rom manager to recreate the EXT3.
Now all ROMs that use the EXT3 run fine!
Click to expand...
Click to collapse
(thanks Kinma for the feedback)
So, i start a search for OTA update file here, and found at "showthread.php?t=885996".
But when i choose "Apply sdcard:update.zip", i got INVALID OPERATION.
Someone have a tip for me about this?
Thanks (its very sad, but i must keep hope).
dogasantos said:
(thanks Kinma for the feedback)
Click to expand...
Click to collapse
You are welcome.
What happened was that after a reboot of the phone the phone started rebooting in the boot sequence, i.e. a boot loop.
I tried a lot of things and nothing worked.
Finally I suspected that the problem might be with the SD card. I had a backup, so I had no problem doing a factory reset.
Then I booted the phone without the SD card.
The phone booted fine.
That way I was certain that the problem was with the SD card.
I had 2 partitions on the SD card, an EXT3 part and the rest was a normal Fat part.
I could still read the card, so I made a backup of all the data on the card.
Then I reformatted the card using windows.
The phone booted fine with an empty, reformatted, SD card.
Since I use Apps 2 SD, I had to recreate the EXT3 partition.
If your rom does not use this, you do not have to do this.
After recreating the EXT partition, put back all files that I want on my SD card.
My advice would be to do a factory reset and after that boot the phone without the SD card.
If the phone boots, you know the problem is with the card.
Hope that helps; good luck!
dogasantos said:
Sorry ask for your help again, but at Official thread (thread number 841207) for DHD files, both 1.72.405.3 links are broken.
So i search for another thread, and found another one, but when i run the .exe, it ask for a USB connection to device, so it appears wrong.
Could you gimme a hand to find the correct file?
PS: I can help with a web hosting to all correct files.
Click to expand...
Click to collapse
Here, use this link:
http://forum.xda-developers.com/archive/index.php/t-899564.html
From "football" post copy and paste his link, the download would start immediately..
Hi folks,
boot without the SD card, doesn't work =(
I'm really without luck with this.
I do:
- Factory reset
- Clear cache and userdata
- Boot without SD or/and SIM cards
- Reflash RUU WWE 1.72.405.3 Radio 26.04.02.17_M2
- Reflash RRU WWE 1.72.405.3 Radio 26.04.02.17_M2 SF
- erase all SD
One show was use OTA update.zip, but at this step i got "invalid operation"
SO, nothing works!
Well, it appears a lost battle =\
thanks folks for all help.
Yeah, there must be something wrong in your device itself, for example a motherboard fault. Send it back to HTC.
yukinok25 said:
Here, use this link:
http://forum.xda-developers.com/archive/index.php/t-899564.html
From "football" post copy and paste his link, the download would start immediately..
Click to expand...
Click to collapse
Hi,
I found the information extremely useful. Big Thanks
GRuti

[Problems & Questions] With Official 2.3 Update V2

Hello !
I am feeling really down today after been trying to get my phone working again.
There is a huge problem currently, I am really annoyed that it doesn't work at all.
First thing, my phone won't start after update it just boot loops and never seem to end it.
First thing I noticed /boot, /cache /system and most things are gone, I can load up recovery but nothing more. I have no idea what happened but the whole image folder was wiped and I had to myself put in the CWM recovery.
I can't do an upgrade "again" as it will be stuck @ the unpacking part without starting it at all.
I been trying with 2.3 V2 and with B133(My stock rom I got).
If anyone has a solution that can solve this problem please help out if you could. Also if you are about to tell me get this and that, please most cases I haven't seen any of the Firmware roms in @modaco wiki links work. Means I can't download them, so if you happen to have spare copy please upload it and link it to me. I have been googling and looking through this section twice, nothing really worked out.
Thanks in advance !
If you didn't erase the .cust_backup partition which contain the image folder with all system' s .img files, then maybe it' s damaged. I had some problems with this partition before and when I checked it with windows check disk it repairs it and I had no problems from then. So, try this, and if you still haven' t any file on image folder, you can find the original folder on X5' s forums. Is definately here, but I don't remember where is the link and I don't gonna search it for you. If you cannot find it, you can allways reflash the original rom. If you fix the partition(if this is the problem), I don't think that you'll have problems with update any more.
dancer_69 said:
If you didn't erase the .cust_backup partition which contain the image folder with all system' s .img files, then maybe it' s damaged. I had some problems with this partition before and when I checked it with windows check disk it repairs it and I had no problems from then. So, try this, and if you still haven' t any file on image folder, you can find the original folder on X5' s forums. Is definately here, but I don't remember where is the link and I don't gonna search it for you. If you cannot find it, you can allways reflash the original rom. If you fix the partition(if this is the problem), I don't think that you'll have problems with update any more.
Click to expand...
Click to collapse
Hello, thanks for the reply.
I have no idea about this .cust_backup partition and how I am supposedly to access it via windows. Also the thing you said about fixing partition within Windows, the check disk thing. I am not sure about that part either as I can load CWM and it can read the partitions but they are empty. Also there is nothing in this forums that contains original things, only way for me to fix this if someone have extra copy and can guide me on how and where to place the all needed files. I am pretty sure it's only things that are missing and I can't get a grip out of this.
So to sum up what my problem is.
I did an upgrade from 2.2 to 2.3 with official firmware, it worked out normally but after a reboot my phone became stuck in an endless loop, I can't do anything and it will not I repeat it will not allow me to "re flash" any firmware I tried so far, the 2.3 V2 and B133.
I am begging someone in this forum section, please if you have the knowledge about this problem care to help?
I can't get a refund out the phone warrenty is off and I do not have that much spare money.
Thanks in advance !
If you can get to recovery, wipe cache and data. It should be possible in stock recovery.
The cust partition has all the images for bootloader, recovery etc. You can get to it with the pink screen. Reformatting and then reinserting the images and files could help, but try that when nothing else works.
I can't give you good help via phone, but try wiping data first. Also, try if you can use some other sd card.
Sent from my U8800 using Tapatalk
Blefish said:
If you can get to recovery, wipe cache and data. It should be possible in stock recovery.
The cust partition has all the images for bootloader, recovery etc. You can get to it with the pink screen. Reformatting and then reinserting the images and files could help, but try that when nothing else works.
I can't give you good help via phone, but try wiping data first. Also, try if you can use some other sd card.
Sent from my U8800 using Tapatalk
Click to expand...
Click to collapse
The most common things I have already done, but do enlighten me what this "custom" parition is. Because in windows I do not see such partition I see a removable partition which I have now added a folder called image with these containing files.
http://forum.xda-developers.com/showthread.php?t=1370960
EDIT ** Also regarding to first person who said about Windows partition manager. The thing is I see a lot of partitions and there is no labeling for them, might be because they are ext2/3 or even something else? In anycase I can't do so much I just find it really odd I have many duplicates and I am guessing that must be errors... Because I am seeing the main recovery partition which has no label too... its at 240 MB where 135MB is used. Lastly there is my internal SD card empty and healthy still I can't reach it within Windows if I do not mount it...And can't now without going into the android OS. I Have loads of free space "partitions I don't understand why they are there".
**
Thanks for helping out, it feels not good to have a half dead phone, it's still not solved :'-(
The .cust_backup is the mount point on android for this removable partition with image folder. In windows haven' t this name. I didn't mean to use the windows partition manager, just to use windows explorer, right click on the partition and choose properties, then tools and then check disk. Of course you can use partition manager too, but because as you found there are all no labeled other partitions there and is a bit confused.
As you mentioned, you found the original image folder and you replaced the files. Did you tried to do the update again after that?
Also you can see and the internal sd partiton, but you need linux system. This partition is not fat32, so windows cannot see it.
dancer_69 said:
The .cust_backup is the mount point on android for this removable partition with image folder. In windows haven' t this name. I didn't mean to use the windows partition manager, just to use windows explorer, right click on the partition and choose properties, then tools and then check disk. Of course you can use partition manager too, but because as you found there are all no labeled other partitions there and is a bit confused.
As you mentioned, you found the original image folder and you replaced the files. Did you tried to do the update again after that?
Also you can see and the internal sd partiton, but you need linux system. This partition is not fat32, so windows cannot see it.
Click to expand...
Click to collapse
I have placed all things that I got from here.
http://forum.xda-developers.com/showthread.php?t=1370960
And I can't run the upgrade firmware, it gets stuck at first stage which is to unpack the the update.app thing.
It just stays like that not blinking and frozen.
Did you tried now that you have the original files, to go to recovery mode and wipe data etc?
Also when you try to do the upgrade do you have the device connected with the cable?
I had this problem once and I think that when I disconnected the cable(or maybe wasn' t connected and I connected it, I don't remember well), the proccess bar starts to moving after a while and the upgrade completed successfully.
dancer_69 said:
Did you tried now that you have the original files, to go to recovery mode and wipe data etc?
Also when you try to do the upgrade do you have the device connected with the cable?
I had this problem once and I think that when I disconnected the cable(or maybe wasn' t connected and I connected it, I don't remember well), the proccess bar starts to moving after a while and the upgrade completed successfully.
Click to expand...
Click to collapse
You are not understanding me :-(, I have wiped already millions of times in millions of different ways just to get it work. And no, I don't have the device connrected when I upgrade, it won't work properly then, I have tried to wait for the progress bar to "start" move it won't happen the battery will die, and nothing happened.
I can't go in with normal Recovery mode, can only go in with CWM, the normal recovery mode is really small, I mean only 3mb, while the froyo version is 5mb. Now I am asking if you have the time to upload the image files from 2.3 V2, the ones in forums are for V1. Which I don't know might conflict.
Thanks again for trying to help me out, this is really frustrating to get it to work.
**EDIT**
I worked it out !
I think I understood what you meant, I did as you told I started first with pluggin in the charger forced it to upgrade and now it's upgrading, thank you so much dancer_69. I was going to go tomorrow to buy a new 2nd hand smartphone. But now I can save my money for other things !
**EDIT of EDIT **
I seem to have downgraded to B133, I will try now with B158 2.3 V2 again and hopefully it will work now.
Yes, wasn't clear because I don' t remember what I've done and solve it. But I think that I did it like you discribed too.
Anyway I'm glad that was helpful(kind of)..
And don' t give up so soon with smartphone' s bricks, I've faced brick kind of problems many times and if the device it' s not completely dead, there is something you can do. Maybe need more search or many tries(sometimes the same things) but at the end(and of course If there isn't a hardware problem) device can unbrick.

Unknown Axon 7

Bought an Axon 7 from China 1.5 years ago. Very satisfied with it, but only got 2 OTA. Last one a couple of months ago. I tried in vain to identify the type. It is marked A2017 on backside. Buildnumber is ZTE_A2017CTJMV1.0.0B04. Is it possible to upgrade manually to Nougat?
Nisse1234 said:
Bought an Axon 7 from China 1.5 years ago. Very satisfied with it, but only got 2 OTA. Last one a couple of months ago. I tried in vain to identify the type. It is marked A2017 on backside. Buildnumber is ZTE_A2017CTJMV1.0.0B04. Is it possible to upgrade manually to Nougat?
Click to expand...
Click to collapse
That is really weird. But of course it is possible
Look, there are three ways to do this. You have the official method, which involves downloading the OTA yourself from the support page, unzipping it, putting it on the internal storage or SD and going to Updates to apply it. This one might fail. Then there's the TWRP way, but you need to unlock the bootloader. And then there's the MiFlash way, where you don't need unlocked bootloader and it will not fail, but it's a little bit of an extreme...
For now, do this:
http://devicedownload.zte.com.cn/support/product/201606031040/sd/20171009174830988.zip
Download that file and unzip it. There will be a file called "update.zip" and maybe a pdf inside. Take the update.zip and put it in the root of the internal storage. Then go to settings -> Updates, and it should detect it. Install it
Thank You
Thanks,
Downloaded and extracted the update.zip file. Put in the root of SD. Tried the system update. Got answer "Software is up to date" But nothing happens.
Nisse1234 said:
Thanks,
Downloaded and extracted the update.zip file. Put in the root of SD. Tried the system update. Got answer "Software is up to date" But nothing happens.
Click to expand...
Click to collapse
Try putting on the internal storage (not the SD card). If it still does not appear, then try updating through the stock recovery. That should work.
EDIT: just to be clear, you did not extract the contents of the update.zip, did you? You need to put the actual update.zip on the internal storage (you can try on the external sd card). As mentioned by choose an username, check the update.zip you downloaded. It it contains another update.zip, that is the file you need. You may have already done this, but I have seen others still get it wrong...
EDIT 2: that being said, your current version number seems strange. I wonder if that is the problem. Maybe the version you are trying to install is not compatible and therefore not seen by the system.
joaste said:
EDIT 2: that being said, your current version number seems strange. I wonder if that is the problem. Maybe the version you are trying to install is not compatible and therefore not seen by the system.
Click to expand...
Click to collapse
That's the point. I wanted to see if the normal update could go normally or not. Next step is MiFlash
At least we know it's an A2017...
Choose an username... said:
That's the point. I wanted to see if the normal update could go normally or not. Next step is MiFlash
At least we know it's an A2017...
Click to expand...
Click to collapse
You can still try first through stock recovery.
Right...
joaste said:
Try putting on the internal storage (not the SD card). If it still does not appear, then try updating through the stock recovery. That should work.
EDIT: just to be clear, you did not extract the contents of the update.zip, did you? You need to put the actual update.zip on the internal storage (you can try on the external sd card). As mentioned by choose an username, check the update.zip you downloaded. It it contains another update.zip, that is the file you need. You may have already done this, but I have seen others still get it wrong...
EDIT 2: that being said, your current version number seems strange. I wonder if that is the problem. Maybe the version you are trying to install is not compatible and therefore not seen by the system.
Click to expand...
Click to collapse
The file "update.zip" contains 29 sub files, none of them was named update.zip.
No I did not unzip it.
This time I put the "update.zip" in the root of the phone folder. But nothing happened when I run the Settings»update.
How do I post screen shots in this forum?
Nisse1234 said:
The file "update.zip" contains 29 sub files, none of them was named update.zip.
No I did not unzip it.
This time I put the "update.zip" in the root of the phone folder. But nothing happened when I run the Settings»update.
How do I post screen shots in this forum?
Click to expand...
Click to collapse
Okay. Put it in the SD card. Then turn the phone off.
After it is completely off, hold Volume Up + power until the zte screen appears. You should get into the stock recovery.
Now, the stock recovery will most probably be in chinese, but you have to use an option that says 'sd' between a bunch of chinese stuff. It's easy to spot. Scroll to that option with the volume keys and select it with Power. The contents of the SD card will appear. Select the update.zip and see if it works or not.
Well...
Choose an username... said:
Okay. Put it in the SD card. Then turn the phone off.
After it is completely off, hold Volume Up + power until the zte screen appears. You should get into the stock recovery.
Now, the stock recovery will most probably be in chinese, but you have to use an option that says 'sd' between a bunch of chinese stuff. It's easy to spot. Scroll to that option with the volume keys and select it with Power. The contents of the SD card will appear. Select the update.zip and see if it works or not.
Click to expand...
Click to collapse
....I have just one mobile. What will happen with data like contacts, apps, bank-id etc?
Nisse1234 said:
....I have just one mobile. What will happen with data like contacts, apps, bank-id etc?
Click to expand...
Click to collapse
Nothing. If you use MiFlash they will get erased, but not this way.
Think about it this way; doing this from the Updates section actually issues a command that gets you into the recovery to flash the file. So basically you skip the Updates part.
Please tell me if the recovery is in chinese later
Nisse1234 said:
....I have just one mobile. What will happen with data like contacts, apps, bank-id etc?
Click to expand...
Click to collapse
Also a small FYI:
-Contacts are backed up on your Google account, and even if you don't have one you can export all of your contacts to a .vcf file, then back it up, and then import it once you finish
-Apps... Just download them again. You can backup the 'Android' folder that's on your internal storage, most games save their data there.
-Bank ID? Isn't that just a log in?
I format my zte axon 7 A2017G and now am stock on WiFi(when ever I tap next it will load then return to WiFi) and it seems the phone is locked by zte please how do I unlock it
Nisse1234 said:
....I have just one mobile. What will happen with data like contacts, apps, bank-id etc?
Click to expand...
Click to collapse
no,but you'd better make a backup .in order to prevent accidents

Categories

Resources