arrgh i dunno whats wrong with my G1 it doesnt boot anymore for some reason
im running on the RC9 SDCard hack version
ive done a wipe and re installation still no success
any help people thank you!
Same problem... waiting for solution.
Did you 2 happen to add something new prior too the 2 points of reboots??
You have to realize, example, if i reboot......install a theme, install the theme, and go on my merry way with my phone. I happen too be one that doesnt reboot for a week. When i do reboot the phone, guess what, it'll lock up on me, if that theme, or whatever, is not meant for my rom.
So try to back track your steps too figure out, what you modded between the two points of rebooting.
My G1 Also hangs.
Hello XDA, long time reader here.
I was wondering if I could get some heads on this one please. My G1 hangs with any non-t-mobile ROM. Here is what I captured from adb logcat... google didn't turn any promising results. Logcat just repeats the following over, and over.
E/AndroidRuntime( 111): Unable to register all android natives
D/AndroidRuntime( 112):
D/AndroidRuntime( 112): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 112): CheckJNI is OFF
D/AndroidRuntime( 112): --- registering native functions ---
W/dalvikvm( 112): ERROR: Unable to find decl for native Landroid/content/res/As
setManager;.getCookieName (I)Ljava/lang/String;
E/JNIHelp ( 112): RegisterNatives failed for 'android/content/res/AssetManager'
pgv100 said:
Hello XDA, long time reader here.
I was wondering if I could get some heads on this one please. My G1 hangs with any non-t-mobile ROM. Here is what I captured from adb logcat... google didn't turn any promising results. Logcat just repeats the following over, and over.
E/AndroidRuntime( 111): Unable to register all android natives
D/AndroidRuntime( 112):
D/AndroidRuntime( 112): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 112): CheckJNI is OFF
D/AndroidRuntime( 112): --- registering native functions ---
W/dalvikvm( 112): ERROR: Unable to find decl for native Landroid/content/res/As
setManager;.getCookieName (I)Ljava/lang/String;
E/JNIHelp ( 112): RegisterNatives failed for 'android/content/res/AssetManager'
Click to expand...
Click to collapse
I have a dumb question, did you root your phone?
Oh my gosh, I'm so neglectful...
I did the 1 touch-root method. (though a similar event happened with manual rooting)
I'm running CyanogenMOD 1.4 + JF recovery image.
I tried to load CyanogenMOD 4.0.1's from the SD card after having wiped/factory state'd the phone.
I'm not in a bad way because i did backup and was able to recover.
Thanks for helping me out
pgv100 said:
Oh my gosh, I'm so neglectful...
I did the 1 touch-root method. (though a similar event happened with manual rooting)
I'm running CyanogenMOD 1.4 + JF recovery image.
I tried to load CyanogenMOD 4.0.1's from the SD card after having wiped/factory state'd the phone.
I'm not in a bad way because i did backup and was able to recover.
Thanks for helping me out
Click to expand...
Click to collapse
I don't take anything for granted anymore. A guy couldn't get the Cyan recovery installed for 3 days and it turned out he hadn't rooted his phone.
Well, the major difference between a Tmobile ROM and the Cyanogen ROM is that the Tmobile ROM will not look for an ext partition during boot. I'm assuming that you have one set up. If so, did you wipe it? That would be my firts suggestion. There is probably something there that is keeping the other ROMs from booting. Wipe it, wipe the phone memory and reinstall the ROM.
The other idea that I had is that you need to check the version of the SPL that you are on. If somehow you were still on the original SPL that would cause a problem.
Mike,
Thanks for the hints. I will try them as soon as I am able. I do not currently have an ext3 partition on my SD card (instructions did not mention such a thing in the order I was following them).
For the sake of complete documentation, I was following the guide on Androidandme.com (http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/)
Here is the strategy I am going to try (assume a card different from my Nandroid backup):
Partition SD card with 1/2 FAT, 1/2 ext3 partition
Format both partitions accordingly
Load Cyanogenmod 4.0.1 on to FAT partition
Execute 1-touch root method on phone
In Cyanogen's Recovery, wipe data
apply Cyanogen's ROM
Make log of boot activity (if failure) -OR- Celebrate with the happy dance.
Is this what you had in mind?
pgv100 said:
Mike,
Thanks for the hints. I will try them as soon as I am able. I do not currently have an ext3 partition on my SD card (instructions did not mention such a thing in the order I was following them).
For the sake of complete documentation, I was following the guide on Androidandme.com (http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/)
Here is the strategy I am going to try (assume a card different from my Nandroid backup):
Partition SD card with 1/2 FAT, 1/2 ext3 partition
Format both partitions accordingly
Load Cyanogenmod 4.0.1 on to FAT partition
Execute 1-touch root method on phone
In Cyanogen's Recovery, wipe data
apply Cyanogen's ROM
Make log of boot activity (if failure) -OR- Celebrate with the happy dance.
Is this what you had in mind?
Click to expand...
Click to collapse
That should work. I glanced over the instructions that you were following. Maybe I missed it but I didn't see it telling you to install the HardSPL anywhere. At the end it said installing the Haykuro SPL was optional. As a part of that process, check which radio and SPL you are on and update those as well if needed. Do that before you install any ROMs.
Moved to Q&A
@pgv100 You said you wanted to partition half your card as ext3. I'm not sure how big your card is, but huge ext3 partitions are not a good idea. Anything under 1GB is fine, personally I use 512mb, and that's waaaay more than I will ever need. So my advise is, choose a size between 256mb and 1GB, anything bigger is overkill and will cause some stability issues.
@Mike,
Thanks for all your help. I'm happy to report what seems to be a consistently rebootable ROM. So, HardSPL was not required. But the change to an ext3 partition WAS required for me.
Thanks again!
@Adrian,
I ended up with a 700ish meg partition (before I read your hint). Looks like I got lucky, huh? Thanks for your hint also.
Related
The error message appears after I flash a Hero ROM and boot, and keeps looping and looping.
Code:
D/AndroidRuntime( 1537): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1537): CheckJNI is OFF
D/dalvikvm( 1537): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 1537): Stale deps in cache file; removing and retrying
W/dalvikvm( 1537): Size mismatch on inflated file (927937 vs 924012)
E/dalvikvm( 1537): Unable to extract+optimize DEX from '/system/framework/services.jar'
D/dalvikvm( 1537): Failed on '/system/framework/services.jar' (boot=1)
D/dalvikvm( 1537): VM cleaning up
D/dalvikvm( 1537): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1537): JNI_CreateJavaVM failed
E/AndroidRuntime( 1537): JNI_CreateJavaVM failed
I've formatted my partitions, repartitioned my SD card every time, and nothing seems to work. I've got the latest radio and Haykuro's SPL, but no class 6 SD card. I'm using a HTC Dream.
Anyone got a clue how I can solve this?
soba5150 said:
flash the new amon RA recovery and from the recovery screen wipe your extension partition and then reflash a rom and let me know what happens
Click to expand...
Click to collapse
Nasrat said:
Try; removing the SD once it say install complete, and then reboot. dont put the SD back until it launches the home screen. and next time please post in the right section.
Click to expand...
Click to collapse
Done those, but they didn't work. I've even rerooted with RC29 over my base CRC1, and it hasn't worked.
Dude go back to rc 29 , let the phone boot up after install .you must let it boot all the way to the home screen ,that means you got to use your Google account.
If that works then you can reboot into recovery, wipe and flash another rom..
The backup you're trying to apply when is it from pre-cupcake rom, cupcake rom, post cupcake rom,? ,
What rom are you trying to install?
I'm already on RC29. I'm currently on CM 4.0.2 and most of the other ROMs don't work for me because of the error posted above. The error message appears after I flash the ROM and boot.
http://forum.xda-developers.com/showthread.php?t=521890
http://forum.xda-developers.com/showthread.php?p=4573316
http://forum.xda-developers.com/showthread.php?t=534663
Try these, ,, happy reading,
dan0zone said:
http://forum.xda-developers.com/showthread.php?t=521890
http://forum.xda-developers.com/showthread.php?p=4573316
http://forum.xda-developers.com/showthread.php?t=534663
Try these, ,, happy reading,
Click to expand...
Click to collapse
It's not a boot loop...I know what that is lol. Boot loops can be solved by wiping ext3/recreating ext3, that I know.
Try to understand, my screen freezes at the G1 logo, and when I logcat it I see that message repeating over and over. My phone does NOT restart at all.
A hero rom
Click to expand...
Click to collapse
is not enough information to make a proper diagnosis. Did you wipe when you went from cyanogen to hero?
Yes I wiped. I did everything you would normally do before you install a new ROM.
The latest roms that don't work for me are:
hero1.7
jacheroski2.2b
hero2-jacski-bfs240b
KiNgxKxROM_v16_signed
update-cm-4.1.999-signed
MLIGN-HeroV2.4.9
Some ROMs work:
DuBZHero_12 (but FC at Home Screen after Setup Wizard)
I'm having this same problem.
I have the same problem too, come on people someone must know whats going on?????????
The only rom thats working for me is kingsklicks eclair. I get the exact same logcat, I think its to do with the dalvik cache, but wiping it has no effect. Ibe tried wipe dalvik via adb but I get an error.
This may be a long shot... but did you try using a different SD card? I've seen it happened before where user would have all kinds of problems which were solved by a new SD card. Perhaps try it with the stock 1gb card just to get an idea? If that fixes it - then you need to get a new SD (class 6). I wouldn't recommend using stock card for apps2sd (too slow).
Sorry if that doesn't help.
Good luck.
maybe you should use de-odexed roms?
I'm unsure if this is two problems or one, but just hoping somebody around here might have a clue what is up with my Nexus.
The background:
Worked my way up through the Cyanogen ROMS without any issue, switching from AmonRa to ClockworkMod about half way through.
Obviously I had to get Froyo on the phone, so installed Paul's and was happily on FRF50.
No issues whatsoever so far, until I noticed FRF72 was about today.
Tried to install the 1.8M patch - and it failed - ah well.
Tried to revert back to FRF50 with my nandroid backup and that failed as well...
..I am now worried.
I deleted some caches - and my nandroid backup worked... then I started fiddling again.. and same errors re-appeared.
Finally got the backup to take again - and I'm now leaving my phone well alone.
The errors:
When trying to install a flash image (every one I've tried so far) I get an error very similar to this one in the log:
...
calling command format
Formatting BOOT:...
mtd: not erasing bad block at 0x00220000
calling command write_raw_image
Writing BOOT:...
mtd: not writing bad block at 0x00220000
E:No space left on device
minzip: Process function elected to fail (in inflate)
E:Error writing BOOT:
E:Failure at line 69:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
Failure at line 6:
install_zip SDCARD:/clockworkmod/download/...
I've just got one bad block listed above, but quite often more than one and on a seemingly wide selection of addresses.
I've not managed to get a single image to install on my phone at all (even going back to the OOB stock image).
When the Nandroid restore fails, it seems to write OK to the boot, but then just hangs locking the entire phone (batter out time) when writing the the data or system partitions.
I ended up going partition by partition to restore the image (2 goes on system, 7th time the charm on data).
The questions:
1) I assume I've got duff blocks on my partitions.
2) I assume I've got so many on root, that space is 'less than expected' - hence the no space left errors?
3) So assuming there's limited space, why does the restore seem to work, but images flashing onto boot fail?
4) Is the issues with nandroid restore likely to be the same (happens with the last 3 backups I've taken)? I don't seem to get a log written as it's just hanging.
5) Is my flash 'degrading' - I'm fine if stuff is marked as duff in the factory, but the ability of my flash seems to still be in a bit of 'flux'
7) Is there anyway I can scan the flash on my phone to get an overall status of the memory (~ChkDsk)?
The Big question:
8) Is there anything I can do, other than get the phone back to HTC?
I'm assuming an inability to flash a standard 'released by google build', would count as being a fault.
Most advice just seems to be to:
a) clear stuff
b) format stuff - oh and you sometimes get the bad block messages.
c) Just don't try to force write to those bad blocks, by writing less to the partition.
d) Google may alter the size of the partitons in the future, so there's enough working blocks for me in each of them.
Any help would be most welcome. I'm feeling quite glum about the whole drama.
hmmm
Im no expert but what Id try is:
1.wipe
2.fresh DL amon_ra again ->flash
3.wipe cache and anyother option
4.fresh DL pauls first fyo50 root rom ->flash
5.wipe
6.fresh DL of the new fyo72 of your choice -> flash
7.wipe
8.fresh DL of clockwork
9.reboot
all your problems seem to have came from clockwork upgrade... once again im no expert, and "I reserve the right to be wrong" lol I love that saying... GOODLUCK bro!
Thanks
Didn't have any luck though.
Boo.
I've been trying to flash the latest nightly or the RC2 and it keeps failing.
I've tried with both recovery-RA-nexus-v2.0.0.img (Amon_Ra) and recovery-clockwork-2.5.0.7-passion.img (Clockwork).
I've tried using radio-4.06.00.12_7.img, FRG83-radio-5_12_00_08.zip, FRG33-radio-5_08_00_04.zip.
I've tried update-cm-6.1.0-RC2-N1-signed.zip and cm_passion_full-274.zip.
I've tried formatting my microSD card.
I've tried downloading each of the files I've mentioned at least twice.
Every time I try to flash either RC2 or any nightly, I get this:
Code:
Welcome to CyanogenMod-6.1.0-RC2-N1!
assert failed: write_raw_image("/tmp/boot.img",
"boot")
E:Error in /sdcard/update-cm-6.1.0-RC2-N1-signed
.zip
(Status 7)
Installation aborted.
On Amon_Ra I did 'Wipe ALL userdata', and it still didn't work.
On HBOOT I did CLEAR STORAGE as well.
I can use adb and fastboot if needed. But the ROMs just don't seem to want to install .
I'm confused and I've googled around but I haven't found any solution.
I was using RC1 previously, if it's relevant.
Any help is greatly appreciated! I don't really like bothering people, but I just can't figure out what to do. I tried searching, I always try searching .
I had a problem flashing stuff with amon 2.0 . I went back to amon 1.9 alpha and everything flashed with no problem. I never used clockwork so i dont know with that. Hope this helps.
After doing some more research I tried
Code:
fastboot boot boot.img
And it let me boot into RC2. I even rebooted and it seems to be working... According to the log, I have some bad sectors.
I tried doing
Code:
fastboot flash boot boot.img
But it gave me an error.
I dont use cmd for anything unless absolutely needed. I just do straightfoward download to sd root and flash through recovery. Maybe the rc2 file your using is bad.
you mentioned bad sectors and such so try downloading a rc2 file from a different site, might work. Try using a different version recovery as well. That could help as well.
u gotta r00t ur gibson first
I am having the same problem.
The bootloader is definately unlocked. I am pretty sure it is rooted as I can use titanium backup and give it root access.... What is the issue?
Maybe it is something related with your HBOOT version. I have mine 0.33.0012 and I have the same error you have. Really my error is in another rom based on 6.1.0RC2 and it seems it is related with the size of the kernel.
Previous kernel was near 1.2MB smaller than this one and maybe HBOOT 0017 manages better internal memory to give space to bigger kernel. Maybe updating HBOOT to 0017 solves this issue.
I am also looking into this problem here at xda to see what experts say
It isn't something as simple as not formating the SD card correctly is it?
No, Status Error 7 means that an image write failed, this is typically because the image doesn't fit on the partition and all of your symptoms point to this. Bad blocks on the /boot partition will cause this.
Old but relevant info I posted some time ago: http://forum.xda-developers.com/showpost.php?p=6851045&postcount=1556 (don't use the files on that page!).
Now, the CM stock kernel is really, really small... so if that doesn't fit then you may have a major challenge installing any custom rom...
I've verified my rom (Kang-o-rama) works on most phones with bad blocks on boot, I spent a lot of time making this so but still, if you have too many bad blocks it will not fit.
One of my users got his Nexus replaced because he had so many bad blocks no kernel would fit once he'd removed the stock one...
Code:
fastboot boot boot.img
Doesn't write the kernel to /boot so you won't encounter the problems (just don't reboot).
Code:
fastboot flash boot boot.img
Attempts to actually write the image.
I think you're in replacement zone actually... if you wipe your current /boot partition you may never get another kernel on there. Be careful.
First of all, sorry for all my possible grammar and usage mistakes, I'm not a native speaker and my English is still rather mediocre. I just couldn't find the solution to my problem and come here though Google.
My problem is that after almost two years of active using my nook HD+ stopped to boot and now behaves pretty much like a brick. I actively used CM10 on emmc all that time without any other upgrades and all went more or less well, until after some installation from Google play all of a sudden the device stopped booting altogether. Unfortunately, I didn’t do any archives.
After some googling I found the thread from the forum on how to recover through downgrading to the stock using the info from the thread: http://forum.xda-developers.com/showthread.php?t=2062613
I prepared the CWM SD (with file :NookHDplus-bootable-CWM-6028-for-stock-BOOTFILES-r4-(05.15.13)) and tried to install plain unrooted factory 2.1.0 (or 2.2.0). Every time just in the middle of installation I got the following messages:
CWM-based Recovery v 6.0.2.8 for HD+ (Stock)
…Installing : /sdcard/NookHDplus –factory-2.2.0-plain-stock.zip…
Opening update package…
Installing update…
Random offset: 0x45
Failed to retouch ‘/system/lib/libemoji.so’
E:Errror in /sdcard/NookHDplus-factory-2.2.0-plain-stock.zip
(Status 7)
Installation aborted.
In another case with NookHDplus-factory-2.1.0-plain-stock.zip I got “Random offset: 0x3da” All the rest of the message was the same as above.
I also tried to install a CWM (v6036) for internal memory (emmc) and Restore stock recovery to emmc (HD/HD+) also with no avail. (I guess so because although I didn’t get any error messages when installing stock recovery from the thread I mentioned above, I still can’t find any traces of stock recovery (v. 6036) on my nook hd+)
And I tried to interrupt the process of booting eight times in a row to facilitate the factory recovery as I read somewhere, also without any success.
I’m not an advanced user, easily could miss somehting important and any help or assistance would be much appreciated.
Alex.
Go to that same thread you referenced and in item 5 it points to a stock recovery you can flash. Flash that and then the 8 failed boot procedure should work, taking you back to stock so you can start over.
It is also possible that your internal memory is bricked (read only) and will accept no changes.
Sent from my BN NookHD+ using XDA Premium HD app
Leapinlar, thank you very much for your advice.
I flashed the stock recovery from item 5 as you mentioned and performed 8 failed reboots. Every time, I turned off my nook emmediatley after I saw the inscription NOOK but before the wheal was shown and then made the 9th normal reboot, and still I got the same wheal as before.
When I flashed the stock recovery, I got the following message after the installation:
CWH-based recovery v.6.0.2.8. fro HD+(Stock)
Installing /sdcard/NookHDplus-emms-stock-recovery-rev0-(05.16.13).zip
Finding update package
Opening update package
Installing update
Installing
Done!
Install from sdcard complete.
I guess the recovery was successfully installed, but for some reason it didn’t work with my failed reboots. Not sure where I made a mistake. Any idea?
aaenaee said:
Leapinlar, thank you very much for your advice.
I flashed the stock recovery from item 5 as you mentioned and performed 8 failed reboots. Every time, I turned off my nook emmediatley after I saw the inscription NOOK but before the wheal was shown and then made the 9th normal reboot, and still I got the same wheal as before.
When I flashed the stock recovery, I got the following message after the installation:
CWH-based recovery v.6.0.2.8. fro HD+(Stock)
Installing /sdcard/NookHDplus-emms-stock-recovery-rev0-(05.16.13).zip
Finding update package
Opening update package
Installing update
Installing
Done!
Install from sdcard complete.
I guess the recovery was successfully installed, but for some reason it didn’t work with my failed reboots. Not sure where I made a mistake. Any idea?
Click to expand...
Click to collapse
You be not doing the 8 failed right. Do it more that 8 times. It should either boot to stock recovery or CWM, depending on which you have in. And it is ok to let it get as far as the cyanoboot logo each time. If you truly have turned the internal memory to read only (bricked), the counter keeping track of the fails will not write and then it won't work. And when the read only happens you are told the write is successful but it really does not take.
Another way to test if the stock recovery took is to try to boot to recovery manually. From powered off, turn it on and hold the power and n key together for a few seconds. Release the power key first before it turns itself back off, followed by releasing the n key. It should boot to recovery, either stock or CWM. If CWM I am afraid you have it bricked.
Sent from my BN NookHD+ using XDA Premium HD app
Leapinlar, thank you once again.
I tried the second option you suggested (boot the recovery manually), and I still get Nook booted by EMC CWM-based recovery v.6.0.3.2 as before. So, my Nook seems to be bricked and nothing can be done to make it working using only software operations, right? ((
Sorry, for the question that may sound silly, but I’m curious if it is possible to install CyanogenMod builds on SD card only and run Nook without internal memory altogether (only on SD); or this is technically impossible and some part of internal memory is necessary anyway to make it working?
aaenaee said:
Leapinlar, thank you once again.
I tried the second option you suggested (boot the recovery manually), and I still get Nook booted by EMC CWM-based recovery v.6.0.3.2 as before. So, my Nook seems to be bricked and nothing can be done to make it working using only software operations, right? ((
Sorry, for the question that may sound silly, but I’m curious if it is possible to install CyanogenMod builds on SD card only and run Nook without internal memory altogether (only on SD); or this is technically impossible and some part of internal memory is necessary anyway to make it working?
Click to expand...
Click to collapse
Yes, verygreen made some older versions of CM that were designed to run on SD with bricked emmc. Search for the term noemmc in the forum.
Sent from my BN NookHD+ using XDA Premium HD app
Some update for my troublesome situation.
I found and downloaded all the files and followed the procedure from the thread
http://forum.xda-developers.com/showthread.php?t=2221289&page=7.
Namely I successfully did everything until the words
“adb push it to /sdcard/ and then install.
Also push and install whatever else you need”
Does “adb push” here means that I necessarily need a Linux run comp, or there’s a workaround for Windows?
Anyways, the size of cm-10.1-20130819-UNOFFICIAL-ovation-noemmc.zip is larger than the size of the disk after burning, and I can’t copy it there. Also, I cant’ apply the gimmick: format another sdcard with SDFormatter, set the first partition as "active" with Mini-Tool Partition Wizard and copy bootfiles from my first sdcard (burned with Win32disk imager) thereafter. Nook doesn’t mount such a sdcard. I tried.
Any thoughts, if there is anything else that can be done on Windows?
aaenaee said:
Some update for my troublesome situation.
I found and downloaded all the files and followed the procedure from the thread
http://forum.xda-developers.com/showthread.php?t=2221289&page=7.
Namely I successfully did everything until the words
“adb push it to /sdcard/ and then install.
Also push and install whatever else you need”
Does “adb push” here means that I necessarily need a Linux run comp, or there’s a workaround for Windows?
Anyways, the size of cm-10.1-20130819-UNOFFICIAL-ovation-noemmc.zip is larger than the size of the disk after burning, and I can’t copy it there. Also, I cant’ apply the gimmick: format another sdcard with SDFormatter, set the first partition as "active" with Mini-Tool Partition Wizard and copy bootfiles from my first sdcard (burned with Win32disk imager) thereafter. Nook doesn’t mount such a sdcard. I tried.
Any thoughts, if there is anything else that can be done on Windows?
Click to expand...
Click to collapse
I don't see the thread and procedure you are talking about. That is an HD thread. But ADB can be set up on Windows. Just look at my HD/HD+ tips thread linked in my signature. Verygreen unfortunately uses Linux and is not much help for Windows users. And that second procedure with setting active, etc is not intended for SD installs.
Sent from my BN NookHD+ using XDA Premium HD app
You could try a fastboot bootable sdcard recovery to fix your partitions.
In some ways I prefer it over a traditional recovery to flash things like, say recovery.img
See my post #16
http://forum.xda-developers.com/nook-hd/help/nook-hd-bricked-flashing-4-4-2-help-t2811998/page2
It's not necessary to have a Linux host (Google fastboot windows), but it will require some adb setup.
Thank you guys for your kind replies. It’ll take probably a while to learn adb from scratch and implement the solutions you suggested and I’m not sure about the duration of this “while”. The OP of the thread, Jon Lee referenced, promised to post back on his progress but never actually did. So, I’m not sure what to think…
Anyways, while searching on how to bypass all the adb related stuff I fond a message of a guy who claimed he was able to do without adb using Linux run Kaspersky Rescue Disk 10.
It actually takes a few minutes to record such a disk but I still have no idea how to find ext4 formatted part of the sdcard and what to do next. Ext4 remains invisible in Dolphin file manager for some obscure reason. I tried to get in touch with the guy but he was not available at the moment.
So, if anyone knows how to use KRD 10 or something like that please write a little bit here about the details of the procedure.
Hi,
Mi Remix mini stuck on boot logo (fisrt one big) only thing I can do is get to the recovery but nothing help to start OS. Any idea?
Zniwiarz said:
Hi,
Mi Remix mini stuck on boot logo (fisrt one big) only thing I can do is get to the recovery but nothing help to start OS. Any idea?
Click to expand...
Click to collapse
We need more detail, first boot? did you root? can you adb? If you rooted first boot took a long time. Did you make a "dd" backup?
oncouch1 said:
We need more detail, first boot? did you root? can you adb? If you rooted first boot took a long time. Did you make a "dd" backup?
Click to expand...
Click to collapse
It stuck after unfinished update. I didn't root it and it wasn't first boot. I can go to recovery but when i click "apply update by ADB" it stuck one more time. I didnt make any backup.
Zniwiarz said:
It stuck after unfinished update. I didn't root it and it wasn't first boot. I can go to recovery but when i click "apply update by ADB" it stuck one more time. I didnt make any backup.
Click to expand...
Click to collapse
Sounds like a bad download of the update, contact jide support since you didn't root. I think they frequent here so how about some help Jide?
I contacted with support, and they will send my new one. I think this isn't only software issue.
Zniwiarz said:
I contacted with support, and they will send my new one. I think this isn't only software issue.
Click to expand...
Click to collapse
Cool you are getting a new unit.
Having played around with many devices, it sure sounds like a software error. If it wasn't warrantied I would have tried to help with it. I bet it will be reflashed and sent out as a refurb.
I sure wish we had a little more lattitude from jide on rooting. It is not evil and the android community thrives on improving devices long after manufactuer support ends. If we only had a custom recovery you wouldn't have had to wait for an exchange.
Keep us posted on your adventure.
I get new from Jide. Meanwhile they released a solution to fix problem and now I owned two Remix Mini working . I had only to reflash it so as U expected it was only software fault.
Cool! Good to know these are kind of brick proof.
Hello. Help to restore the firmware. It shows only a black screen with the word remix
Sorry for my bad english
Log
fs_mgr: begin to format ext4 buffer : /dev/block/mmcblk0p12fs_mgr: finish format to ext4: /dev/block/mmcblk0p12fs_mgr: exec: pid 1610 exited with return code 1: Unknown error 256fs_mgr: begin to format ext4 buffer : /dev/block/mmcblk0p12fs_mgr: finish format to ext4: /dev/block/mmcblk0p12fs_mgr: exec: pid 1611 exited with return code 1: Unknown error 256fs_mgr: begin to format ext4 buffer : /dev/block/mmcblk0p12fs_mgr: finish format to ext4: /dev/block/mmcblk0p12fs_mgr: exec: pid 1613 exited with return code 1: Unknown error 256fs_mgr: begin to format ext4 buffer : /dev/block/mmcblk0p12fs_mgr: finish format to ext4: /dev/block/mmcblk0p12fs_mgr: exec: pid 1614 exited with return code 1: Unknown error 256
Click to expand...
Click to collapse
You will need a file from Jide. Press f2 key during startup and install the update. I guess you need to contact Jide support first ask for a recovery file.