Database Users

[HELP] - Soft bricked? -SOLVED-

Hi guys, I think I soft bricked a galaxy note, this is the things I did (I was trying to install ICS Stunner)
It came with the kernel KK8 that is non rootable, so I downgrade it to KJ1 (SGN_XX_OXA_KJ1_FACTORYFS) and it worked fine.
Flashed the Abyss kernel (AbyssNotekernel42CWTouchCustomLogo) via CWM and rebooted again to recovery
Flashed ICS Stunner (ICS_Stunner_Beta5.0) via CWM and FORGOT to wipe data/cache so it got in a boot loop
Booted again to CWM and wiped data/cache and still the rom wouldn't boot, so I decided to flash again the rom
The rom wouldn't flash via CWM I mean I selected the zip but the process wouldn't advance, same with the abyss kernel
So decided to start all over again and reflashed KJ1 via Odin (it was sucessfull), but now stock rom won't boot, if I shut down the phone and connect the charger the battery animation stays emtpy, I mean no green bar filling or nothing
The device can get to download mode, but I don't know what to do now, reflash another stock rom?
flash with heimdall?
If anyone can help it would appreciate.
Oh by the way, all this stuff was with the battery at like 20% (I know, pretty stupid)

You lost root during the process.Can you go again in download mode and flash with pc odin stock gb rom?
try this one 3*Files Wipe N7000XXLC1_N7000OXALC1 Open Europe (02/03/2012) from here
http://forum.xda-developers.com/showpost.php?p=23357737&postcount=1
if the flash is succesfull you may go in boot loop.remove the battery put it again in,with volume up+home+power go to stock recovery and do wipe cache and wipe data/factory reset .reboot
Sent from my GT-N7000 using Tapatalk

thanx man, downloading now

Dude i think u forgeted to flash ics repack before flashing ics stunner. .
Sent from my GT-N7000 using XDA

damn I tought it was not necesary on ics stunner 5.
Anyways the battery is full dead, had to go to buy an external charger and now is charging

maxthebest685 said:
Dude i think u forgeted to flash ics repack before flashing ics stunner. .
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Actually yes (this is the method i prefer) but he followed the instructions
"NEW STEPS BETA 4.3 ONWARDS:
Backup data apps.
Download and copy latest Stunner ROM on your SD Card.
Make sure you are on Rooted ROM. Reboot in recovery.
ONLY IF YOU ARE ON GINGERBREAD: Flash Abyss Kernel. Goto Advanced and Reboot Recovery.
Wipe Data (Recommended but not mandatory if you on Stunner ROM already)
Flash ROM.
Flash suitable Modem (Optional, recommended ICS LP5 modem)(not included in ROM)
Reboot and Read Caution.
Do not restore system apps or system data."
one think that may brake the procedure is he may come from a not properly rooted gb rom.I always mount system and always copy-paste some test files to /system in order to be sure sure that i did not lost root.I hope to solve your problem

i had the same issue two days ago nothing serious tried wiping factory but each and every move got the process stock at the beginning so at last i got it charged about 60% then went to download mode and flashed a GB ROM (STOCK) after all with the stock packages odin doesn't inscrease flash count so not to worry just get it to work again and next time wipe cache (preferable factory reset too) i recommend this step, then flash a repack LP1 of Chainfire to get things moving wouldn't take too long with a 90% power you can do all of these steps without any problem dont be paranoid......

oh god this -> Rooted_Stock_Odex_N7000XXLC1 saved me, thanx guys, the phone has booted, I have a captivate and never had this kind of issues the GNote its not even mine.
So just to know, for ics stunner 5 I need to flash first the ics repack

Yep. If you're properly rooted (and with that pre-rooted rom you are) then just install CWM recovery and Mobile Odin, flash the ICS repack, reboot to recovery, flash Stunner and then wipe data/cache/Dalvik, reboot and you should be good to go.

stunner 5.0 beta
what a rum the best is the Stunner beta 5.0 LP6_Kernel_repack may recommend a different kernel is not as happy with a repack
MIDNOTE2.1_BASE or Stunner beta 5.0

N7000 BrickProof Method of doing Factory Reset on Stock ICS-No root or custom kernel

If that is all you want to do, just go to Phil3759's post here http://forum.xda-developers.com/showthread.php?t=1849737 (Many thanks to him) Tested and definitely works on Galaxy Note.
If you want more options (Including safe Nandroid backup and restore), then read on:-
I have signed some files that make it possible for them to be flashed from STOCK ICS 3e recovery. (ie. boot into Stock recovery and select "apply update from external storage" and flash)
Download signed Abyss kernel and put it on your externel SD card. (It doesn't root your phone and has been proven safe over a long period of time)
Abyss Note RedPill Touch http://d-h.st/TZW
Now download latest LRQ ICS stock kernel http://d-h.st/EZH and also put it on external SD card.
OK lets start:
- If you are on non-rooted stock ICS and just want factory reset, flash Abyss from external storage and straight after that, do 3 finger salute (volume up + menu + power) to boot back into Abyss (remember it's GB so no point letting ICS boot up), and do wipes. (Why not do Nandoid backup while you are there? Just remember to flash LRQ kernel after restore)
Then flash LRQ kernel file and reboot. You are now on ICS with latest Stock kernel:good:
- If you want root with safe kernel go here http://forum.xda-developers.com /showthread.php?t=1789397 and download Universal or Touchwiz kernel of your choice and put on external SD. Flash Abyss, boot back into it and then flash custom kernel. You are now rooted with safe kernel
- If you want to try custom ROM (Any), do the following:- Flash Abyss, reboot into it and do factory reset, wipe cache and Dalvik cache. Now go to "mounts and storage", format/system, mount partitions that are not mounted and then flash ROM
Happy days and good flashing:laugh:

GB recovery
Hi, it is wonderful!, has it been tested to work in stock gingerbread?

zopilote said:
Hi, it is wonderful!, has it been tested to work in stock gingerbread?
Click to expand...
Click to collapse
I don't think Stock GB recovery allows for flashing of signed files. In any case GB is safe for wiping. If u want root, go here http://forum.xda-developers.com/showthread.php?t=1329360

shoey, you are the epitome of innnovation
the only problem is you are way ahead ...
i would love for our community to certify this
you do have a Note and tried this right ?

rraaka said:
shoey, you are the epitome of innnovation
the only problem is you are way ahead ...
i would love for our community to certify this
you do have a Note and tried this right ?
Click to expand...
Click to collapse
Sure have. About 7 or 8 times now. No problems at all
In fact I have just gone from stock LRQ to JellyCore and back to stock LRQ again.
ie; flash and boot into Abyss, do Nandroid backup, do wipes/system format, Flash JellyCore, play with it a bit, boot into recovery, wipe and format again with Abyss, do Nandroid restore, reflash LRQ kernel and reboot. Back on stock LRQ again. (even Samsung wouldn't know what I did)

Bravo's bootloader

Hello
I have Motorola Bravo, everything stock 2.2.1 ROM
but I want to install custom ROMs and I have one question: Does Motorola Bravo's bootloader need unlock? I ask that, because I also have Motorola Atrix 4G and I had to unlock it's bootloader to install Cm7

Enigmavision said:
Hello
I have Motorola Bravo, everything stock 2.2.1 ROM
but I want to install custom ROMs and I have one question: Does Motorola Bravo's bootloader need unlock? I ask that, because I also have Motorola Atrix 4G and I had to unlock it's bootloader to install Cm7
Click to expand...
Click to collapse
No, just install 2nd-init recovery (search the Defy Forums\CM7 threads here) then flash away . Our bootloader is locked up like a con in a SuperMax with a triple life sentence. I'm getting ready for work so I don't have time to hotlink.

skeevy420 said:
No, just install 2nd-init recovery (search the Defy Forums\CM7 threads here) then flash away . Our bootloader is locked up like a con in a SuperMax with a triple life sentence. I'm getting ready for work so I don't have time to hotlink.
Click to expand...
Click to collapse
Here you go: https://www.box.com/shared/p07z8hangnqxydducrhr.
Edit: on a side note, I've had issues restoring my JB nand from the cm7 recovery. I get "error restoring system" in the middle of a nand restore. It also completely screws up mounts and the only thing I can do is install a ROM from scratch. The md5 checks out as well. Any ideas?

Dr. Orange said:
Here you go: https://www.box.com/shared/p07z8hangnqxydducrhr.
Edit: on a side note, I've had issues restoring my JB nand from the cm7 recovery. I get "error restoring system" in the middle of a nand restore. It also completely screws up mounts and the only thing I can do is install a ROM from scratch. The md5 checks out as well. Any ideas?
Click to expand...
Click to collapse
JB has a newer recovery. Install a JB rom then restore the nand of the JB backup.
Flash JB rom (cache\data wipes don't matter since you won't be booting into the system)
Reboot directly into recovery (don't let the system boot up, even once)
Restore JB Backup as usual
This is actually a common problem with Defy users running older MS2 roms trying to flash JB -- the different recovery versions can be a pita to deal with sometimes; but its usually fixed by flashing a rom with a compatible recovery version then restoring the nand afterwards.
While I won't go into the full details, you can also take the recovery from a JB rom and a GB rom and make them into a flashable zips -- basically open the rom's zip and delete all the /system folders except /system/bootmenu and edit the rom's updater-script to only set permissions to /system/bootmenu. It would also be a good idea to add in ramdisk backup commands as well (the init.rc files under 2nd-init and 2nd-boot) since they can change from rom to rom. Once all that's done you'll be able to flash the required recovery version for the nand you intend to restore or flash the JB recovery after flashing any rom and have an up-to-date recovery with an older rom. If you use multiboot it would be a good idea to merge it into your new recovery zip as well.
/About to test a CM7 port with many tweaks -- if it boots I'll start adding in some market apps and finish it up later today . Then its off to start updating PA with a Custom Kernel . I may have to drop MS2 PA support if the MS2's Custom Kernel differences makes it incompatible with the Defy base

skeevy420 said:
JB has a newer recovery. Install a JB rom then restore the nand of the JB backup.
Flash JB rom (cache\data wipes don't matter since you won't be booting into the system)
Reboot directly into recovery (don't let the system boot up, even once)
Restore JB Backup as usual
This is actually a common problem with Defy users running older MS2 roms trying to flash JB -- the different recovery versions can be a pita to deal with sometimes; but its usually fixed by flashing a rom with a compatible recovery version then restoring the nand afterwards.
While I won't go into the full details, you can also take the recovery from a JB rom and a GB rom and make them into a flashable zips -- basically open the rom's zip and delete all the /system folders except /system/bootmenu and edit the rom's updater-script to only set permissions to /system/bootmenu. It would also be a good idea to add in ramdisk backup commands as well (the init.rc files under 2nd-init and 2nd-boot) since they can change from rom to rom. Once all that's done you'll be able to flash the required recovery version for the nand you intend to restore or flash the JB recovery after flashing any rom and have an up-to-date recovery with an older rom. If you use multiboot it would be a good idea to merge it into your new recovery zip as well.
/About to test a CM7 port with many tweaks -- if it boots I'll start adding in some market apps and finish it up later today . Then its off to start updating PA with a Custom Kernel . I may have to drop MS2 PA support if the MS2's Custom Kernel differences makes it incompatible with the Defy base
Click to expand...
Click to collapse
Yep that makes sense. Thanks for the help as always skeevy.
*edit* Same issue.
Restoring system...
Error while restoring /system!
Problem while restoring system!
Maybe I didn't reboot correctly...bad backup maybe? I've restored this backup before with no problems. : \
*edit again* I goofed. Your instructions worked fine.

[Q] What should i do to flash stock kernel?

HI all, I have a Rooted N10 (Android 4.3) with KTmanta Kernel and stock ROM. Before installing KTmanta kernel i made a Nandroid Backup. Now if i want to go back to the Stock Kernel what should i do? Is it SAFE to flash the "Boot.img" in the original nandroid backup? I believe it contains the kernel. Thanks in advance.

mfaisal98 said:
HI all, I have a Rooted N10 (Android 4.3) with KTmanta Kernel and stock ROM. Before installing KTmanta kernel i made a Nandroid Backup. Now if i want to go back to the Stock Kernel what should i do? Is it SAFE to flash the "Boot.img" in the original nandroid backup? I believe it contains the kernel. Thanks in advance.
Click to expand...
Click to collapse
It's fine to restore the boot.img from your backup as boot.img does contain the kernel. What I usually like do in this situation is I download the stock 4.3 boot.img (Which can be extracted from the latest Nexus 10 factory image from here https://developers.google.com/android/nexus/images#mantarayjwr66y) and then flash it in fastboot with the command:
Code:
fastboot flash boot boot.img
This will restore your stock kernel. Let me know if you still have questions.
Sent from my SCH-I535 using XDA Premium 4 mobile app

shimp208 said:
It's fine to restore the boot.img from your backup as boot.img does contain the kernel. What I usually like do in this situation is I download the stock 4.3 boot.img (Which can be extracted from the latest Nexus 10 factory image from here https://developers.google.com/android/nexus/images#mantarayjwr66y) and then flash it in fastboot with the command:
Code:
fastboot flash boot boot.img
This will restore your stock kernel. Let me know if you still have questions.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am much thankful for your help Infact, I do have a question related to flashing kernel. I have read in related articles that after flashing any kernel you must perform the following in the CWM recovery: 1. Delete cache 2. Wipe dalvik cache 3. Fix permissions.
I am using CWM Recovery 6.0.4.3 (the latest for N10 downloaded from CWM website) and it doesn't offer the option of FIX PERMISSIONS. So the last time i flashed KTmanta kernel i couldn't possibly use option no. 3 above. My N10 is running smoothing without any issues. But the thing is, I am asking because I do want to follow the steps as directed by the author of the kernel or the ROM. Thanks in advance

mfaisal98 said:
I am much thankful for your help Infact, I do have a question related to flashing kernel. I have read in related articles that after flashing any kernel you must perform the following in the CWM recovery: 1. Delete cache 2. Wipe dalvik cache 3. Fix permissions.
I am using CWM Recovery 6.0.4.3 (the latest for N10 downloaded from CWM website) and it doesn't offer the option of FIX PERMISSIONS. So the last time i flashed KTmanta kernel i couldn't possibly use option no. 3 above. My N10 is running smoothing without any issues. But the thing is, I am asking because I do want to follow the steps as directed by the author of the kernel or the ROM. Thanks in advance
Click to expand...
Click to collapse
When your flashing a kernel in recovery it's important to follow the directions provided by the kernel developer. Deleting chache, and wiping dalvik cache are essential to ensuring the kernel runs properly and doesn't bootloop your phone are you flash the kernel. As far as fix permissions this utility was removed for recovery because the way it was implemented was outdated and broken, fix permissions is more of a helpful option rather then a necessity in this situation. If you really want to run fix permissions you can download and run Stericson's Fix Permissions App. If you need me to clarify any of my points or anything else let me know I'll be happy to do so.

shimp208 said:
When your flashing a kernel in recovery it's important to follow the directions provided by the kernel developer. Deleting chache, and wiping dalvik cache are essential to ensuring the kernel runs properly and doesn't bootloop your phone are you flash the kernel. As far as fix permissions this utility was removed for recovery because the way it was implemented was outdated and broken, fix permissions is more of a helpful option rather then a necessity in this situation. If you really want to run fix permissions you can download and run Stericson's Fix Permissions App. If you need me to clarify any of my points or anything else let me know I'll be happy to do so.
Click to expand...
Click to collapse
Thanks again for your prompt reply I don't think i really need to run "fix permissions", as long as my ROM is running good. I am happy that I at least know how to do that in case i am in real need of running fix permissions. God bless you

[Q] CWM Boot Loop

Hi,
I installed CWM v6.0.5.3 from the CM11 thread here onto my rooted stock rom so that I could do a nandroid backup.
It installed OK and I did the backup but now it always boots into CWM!
When I select "reboot system now" it also complains that "root access it missing". Selecting yes to root device doesn't get rid of this message on subsequent boots.
I can still get into download mode and I can use Odin to re--flash stock rom which enables me to boot correctly, but then I've lost all my data. Ironically I only installed CWM to do a backup and I don't have any other backup!
I can see other threads with similar problems but they're on other devices and the fix.zip's don't work on the Y.
I'd appreciate any help.
Regards,
Paul.

Some more info...
Even after flashing the stock ROM and re-installing CWM 6.0.5.3 I get the same issue.
I've tried using a temporary CWM v5 but this is unable to restore the backup.
Thanks...

Just thinking out loud now...
Is there a way to manually restore data.yaffs2.img from the backup without installing CWM 6.0.5.3?

It's not a problem. On flashing CWM 6.0.5.3 it converts the system to MTD from RFS which prevents it from booting due to lack of compatible ROM. CWM 6.0.5.3 can't be used with any GB or ICS ROM. It needs KK and for that you have to flash CM 11. Hope this helps.

pda1ey said:
Hi,
I installed CWM v6.0.5.3 from the CM11 thread here onto my rooted stock rom so that I could do a nandroid backup.
It installed OK and I did the backup but now it always boots into CWM!
When I select "reboot system now" it also complains that "root access it missing". Selecting yes to root device doesn't get rid of this message on subsequent boots.
I can still get into download mode and I can use Odin to re--flash stock rom which enables me to boot correctly, but then I've lost all my data. Ironically I only installed CWM to do a backup and I don't have any other backup!
I can see other threads with similar problems but they're on other devices and the fix.zip's don't work on the Y.
I'd appreciate any help.
Regards,
Paul.
Click to expand...
Click to collapse
You didn't install cwm6 - you flashed a kernel only meant for cm11 that has cwm6 built in - this kernel will not work on stock roms
Simply mount system then flash a stock based kernel like hells fusion #50
In future use cwm5 to make backups of stock roms - hells fusion kernel has it built in

Ah, and I thought I was being clever by going for the latest version!
I'll try flashing that kernel and let you know...

Hi,
From CWM 6.0.5.3 I mounted /system and installed hells fusion #50, but the phone still boots into CWM 6.0.5.3.
I tried also installing the stock kernel from the aroma installer, but still ended up in CWM 6.0.5.3.
Regards,
Paul

pda1ey said:
Hi,
From CWM 6.0.5.3 I mounted /system and installed hells fusion #50, but the phone still boots into CWM 6.0.5.3.
I tried also installing the stock kernel from the aroma installer, but still ended up in CWM 6.0.5.3.
Regards,
Paul
Click to expand...
Click to collapse
Maybe its a build.prop issue with the zip and not flashing it
Try flashing a stock kernel via odin like the following (place in pda)
http://d-h.st/18f
If not you will have to flash an entire stock rom firmware via odin

I tried flashing that kernel with Odin, but when I boot I just get stuck on the Samsung logo.
Thanks for your help and time, but it looks like the backup I took with v6 isn't of any use, and I'll have to start again from fresh.
But I might run with Hell's Fusion as that looks good!
The reason I started all this was because the phone keeps messing up whilst in a call e.g. putting the call on hold, or speaker. I've tested the proximity sensor and thats OK, so I was going to try a custom ROM to see if that cured the problem.

pda1ey said:
I tried flashing that kernel with Odin, but when I boot I just get stuck on the Samsung logo.
Thanks for your help and time, but it looks like the backup I took with v6 isn't of any use, and I'll have to start again from fresh.
But I might run with Hell's Fusion as that looks good!
The reason I started all this was because the phone keeps messing up whilst in a call e.g. putting the call on hold, or speaker. I've tested the proximity sensor and thats OK, so I was going to try a custom ROM to see if that cured the problem.
Click to expand...
Click to collapse
If you can get into recovery now it should be cwm5
You can try flashing hells fusion now and see if it boots - if not flash stock rom via odin

Where i can see the hell fusion #50