Database Info

[Q] Urgent - Boot loop and unable to restore to stock.

Alright guys, I've got a question. I have my brothers nexus s that has had CM9 A11 on it and we decided to move to the latest CM9. Long story short, I am no longer able to boot the phone up, but can only access CWM Recovery and Bootloader/Fastboot mode. Trying to boot results in a bootloop. I need help getting this thing back to stock however I can. I've tried to flash recovery.img via fastboot but cannot get my computer to recognize the phone in order to do what I need. He would like his phone back ASAP and I hate to tell him its bricked for a few days. Thanks!

Download full OTA ROM from the link in my signature. Boot into CWM, mount USB storage, and transfer the file to SD card. Flash it. Done.
Just make sure you download the correct ROM for your phone model.
Sent from my Nexus S using xda premium

Video on that page will show you how to install drivers on a windows-based machine to recognise the phone for fastboot, and provide files to do so.
Also, can't you go into CWM --> mounts and storage --> mount usb storage (while plugged into the computer) then copy over any files you need, then flash through recovery.

I forgot to mention that I am getting this when trying to format cache:
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/command
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/latest_log
E:Can't open /cache/recovery/latest_log
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
I tried to install the OTA update like you said but got the following:
assert failed: write_raw_image("/tmp/boot.img".
"boot")
E:Error in /sdcard/(OTA file name here)
(status 7)
Installation aborted.
Maybe the internal SD card is bad? Any thoughts?

When you get the drivers installed, download the latest 5.0.2.0 CWM from here.

Alright, so I got fastboot to recognize the phone, but am having another problem. It gave me an error when I gave the command to flash the new CWM. I tried to install pdanet for the drivers, and the phone says at the bottom "FASTBOOT STATUS - FAILInvalid Command". I really think something has been corrupted, any ideas on how to fix it/restore it? Thanks for all the help guys.

Fastboot status is not a command.
Fastboot devices is the command you use to test if it sees the device . The serial number will show.

uh oh sounds like someone flashed brickROM V1
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.

huawei u8815 g300 bricked?

Hi guys,
Had a thread open on modaco for this issue but had no joy. I'm having exactly the same issues as the thread starter in the link below, you guys have helped me before and wondered if you had any suggestions on a way forward?
http://www.modaco.com/topic/358071-phone-near-bricked-help-needed/
Basically I've had ics updated on the phone with the boot loader unlocked and of course the phone rooted. The update went through fine and I've been using the phone for a couple of days until it crashed and stuck on the splash screen since then it will only go into recovery mode with the following errors:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Have tried wiping cache, formatting cache and numerous other things as per the thread on modaco but no joy. I've literally had the phone a few days and think it's unlikely to be a hardware fault unless it's exactly the same as the OP had.
Willing to try anything!
Thanks

Bricked acer a100

Respected friends,
About a week ago my tablet got bricked , after a little research i was able to understand that the update.zip method which sadly didnt work for me. Here i would like to explain how i tried it ,
1/ download from a foreign website about 300 mb file
2/format sdcard(fat32) then operate the microsd card using mobile phone slot-transfer via usb port
3/ copy paste the file as update.zip (name shows as 'update' only)
4/put it in the tablet
5/press vol+ & power i see 'erasing cache before sd update'; and then nothing different occurred just a dead android sign
under android system recovery 3e: i get few options but none show up with results. ( in blue)
and a bunch of errors in yellow:
E: cant open/dev/block/mmcblk0p5
(no such file or directory)
e: failed to moun / cache ( no such file or directory)
e:cant mount / cache/recovery/command
e; failed to mount /cache ( no such file or directory)
e: can mount /cache/recovery/last_log
e;cant open /cache/reoery/last_log
e failed to mount / cache( no such file or directory)
e cant mount /cache/reovery/last_install
e; cant open / cache/recovery/last_install
e: cant open/dev/block/mmclk0p5
(no such file or directory)
e: failed to moun/ cache ( no such file or directory)
so that's the errors i get also very importantly i would like to share:
as you see this method obliviously seems that it didnt work and so i hadn't touchd the tablet for like a week. But a day before my first retry seemed somewhat successful: the method was same but instead it showed me a bar loading and the dead android (now the bar loading seemed some sort of progress which i m unable to achieve again and i wasn't able to put it on charge during that period of time)
Now i know there are alot of ways out there to achieve the required state but i just wasnt sure which one to follow and how ... and i hope i will be guided properly here
Regards
F22archrer

[Q]Datawind UbiSlate 7c+ edge tablet cwm loop

I flashed my ubislate 7c+ edge with the wrong recovery, and i believe it wiped all partitions.I have already tried every possible method found in any nook and corner of the internet.
I'm stuck in cwm recovery loop, it will boot to nothing but cwm recovery.
LiveSuite isnt working, i have like 4-5 images out of which atleast ONE of them must be the correct firmware(all of these i found on xda and the internet which was said that it would work) BUT none work since partitions are gone...
recovery says like cant mount system
cant mount emmc.... etc
Pheonix card doesnt work either, shows sprite error
I can make neither head nor tail of it.
Can anyone show me a way with which i could manually fix this tablet by either writing the partitions manually somehow or doing some magic trick(lol)? Please enlighten me.:crying::crying::crying:

bump
Edit : Hot news !!
After months of pure hopelessness ! I opened my back cover(for the 3rd time), moved the sticker and noted the board number(pcb number i guess?).
A sticker was covering it from being seen lol ! I noted it and googled the number.Found 3 firmwares for it. The first showed nothing in livesuit 1.07. Went till 3% and nothing happened. In livesuit 1.11 it showed x162 error(for a gazillionth time).I was hanging on the edge now. Had downloaded only 2 firmwares.
Tried the 2nd one and boom ! it went past 4% and i watched with glee as upgrade succeeded!! So my partition was wiped, but this managed to rewrite it.(Pats myself).
No datawind logo on boot. Everything works perfectly.
Link to working rom.I'll never try to upgrade this thing again lol .

NoobInToto said:
bump
Edit : Hot news !!
After months of pure hopelessness ! I opened my back cover(for the 3rd time), moved the sticker and noted the board number(pcb number i guess?).
A sticker was covering it from being seen lol ! I noted it and googled the number.Found 3 firmwares for it. The first showed nothing in livesuit 1.07. Went till 3% and nothing happened. In livesuit 1.11 it showed x162 error(for a gazillionth time).I was hanging on the edge now. Had downloaded only 2 firmwares.
Tried the 2nd one and boom ! it went past 4% and i watched with glee as upgrade succeeded!! So my partition was wiped, but this managed to rewrite it.(Pats myself).
No datawind logo on boot. Everything works perfectly.
Link to working rom.I'll never try to upgrade this thing again lol .
Click to expand...
Click to collapse
first procedure got error
*********************
CWM-based Recovery v
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/lost_log
E:Can't open /cache/recovery/lost_log
--- installation /sdcard/rom.zip
E:Can't mount /cache/recovery/last_install
E:Failed to open last_install: No such file or directory
second procedure got errors
******************************
UbiSlate 7c+ start only in recovery mode
and display following messages
CWM-based Recovery v6.o.1.2
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
trying to recover with recovering backup
it will display an error message like
Checking MD5 sums........
Erasing boot image...
Restoring system.......
E:format_volume: make_extf4fs failed on /dev/block/nandd
error while formatting system
is there any solutions for that
phonix card got error

aasifnasim said:
first procedure got error
*********************
CWM-based Recovery v
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/lost_log
E:Can't open /cache/recovery/lost_log
--- installation /sdcard/rom.zip
E:Can't mount /cache/recovery/last_install
E:Failed to open last_install: No such file or directory
second procedure got errors
******************************
UbiSlate 7c+ start only in recovery mode
and display following messages
CWM-based Recovery v6.o.1.2
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
trying to recover with recovering backup
it will display an error message like
Checking MD5 sums........
Erasing boot image...
Restoring system.......
E:format_volume: make_extf4fs failed on /dev/block/nandd
error while formatting system
is there any solutions for that
phonix card got error
Click to expand...
Click to collapse
Dude. You need to flash ROM via livesuit. Nothing else will work I promise.
Unzip that file and you will find the image to flash.
Good luck.

NoobInToto said:
Dude. You need to flash ROM via livesuit. Nothing else will work I promise.
Unzip that file and you will find the image to flash.
Good luck.
Click to expand...
Click to collapse
i also did that
but it goes upto 3% and gives and error after 3% update

aasifnasim said:
i also did that
but it goes upto 3% and gives and error after 3% update
Click to expand...
Click to collapse
What tablet do you have? Where is the camera located?

Dear Sir/Madam,
Greetings of the Day.
We regret any inconvenience caused.
This is to inform you that kindly share your contact no so that we can assist you further regarding the Service Center address.
Alternatively you can contact our support number at 18601800013.
Thank you so much for your patience and co-operation.
Regards,
DATAWIND INNOVATIONS.

[Q] * [Discussion : Inputs from Android Experts] *Topic: BOOTLOOP / NAND WRITE FAIL*

Hello XDA community,
I am proposing this thread as a common knowledge base on
Rampant Nand Write Fail issue.
Having searched through numerous forums here & on Internet, i concluded no working solution on it.
Many have accepted fate of their devices - Dead .. and put them in storerooms.
For rest frantic people out there eating into *help me* lines , they will soon accept the same.
So, the purpose of this thread is to Analyze why did it happen, than to expect a Resurrection .
Having been a victim of NAND WRITE Fail, here are my Final thoughts :
Characteristics of problem :
1. BootLoop
2. Typical of Kitkat OS
3. Download mode available
4. Recovery mode unavailable
- flashes open-stomach android logo for split second , BootLoop again.
5. Happened in devices that initially did not come with KNOX,
but were upgraded to Kitkat with KNOX.
Observations :
1. Changing System / USB 2.0 port - did not solve.
2. Changing versions of ODIN - did not solve
3. Re-flashing of Stock 4.4.2 ROM - Failed [NAND Write Fail]
4. Flashing of older Stock ROMs - Failed [NAND Write Fail]
- also gathered info : You can not downgrade since Kitkat Bootloader wont allow.
5. With ONLY Download mode accessible,
- Not a single tar was successfully Flashed onto device.
- All recovery tar files fail to flash [NAND Write Fail]
Conclusion to Discuss with Experts :
1. Write to NAND memory is being blocked by something [Boot Loader ? ]
2. NAND memory itself is damaged.
- Unlikely seeing the wide scale of this problem.
3. Why is Download mode accessible,
and what causes a flash-second opening into Recovery mode... then Reboot.
4. What role has KNOX to play here [Trying to root tampered with WHAT PART OF KNOX Rule] ?
5. What do we know about bootloader in this context ?

thanks for opening this thread.
I have the same problem with my M480W.
However I am able to enter recovery mode, yet nothing works ...
Code:
E: failed to mount / system (Invalid argument)
can't mount '/system' (invalid argument)
E: failed to mount / system (Invalid argument)
E: File Open error '/cache/recovery/log'
E: can't open /cache/recovery/log
E: File Open error '/cache/recovery/last_log'
E: can't open /cache/recovery/last_log
E: File Open error '/cache/recovery/last_install;'
E: can't open /cache/recovery/last_install
I havent yet tried to repartition, cause I cannot find the correct pit file for my model.

Megatronicalite said:
thanks for opening this thread.
I have the same problem with my M480W.
However I am able to enter recovery mode, yet nothing works ...
Code:
E: failed to mount / system (Invalid argument)
can't mount '/system' (invalid argument)
E: failed to mount / system (Invalid argument)
E: File Open error '/cache/recovery/log'
E: can't open /cache/recovery/log
E: File Open error '/cache/recovery/last_log'
E: can't open /cache/recovery/last_log
E: File Open error '/cache/recovery/last_install;'
E: can't open /cache/recovery/last_install
I havent yet tried to repartition, cause I cannot find the correct pit file for my model.
Click to expand...
Click to collapse
PIT Has not solved this problem on any device i know...
Per my knowledge from various posts, they all ended up finally making it a 'Paper Weight' .

Has anyone found a solution?