Please forgive me and point me to the correct board to post this if I am in the wrong place.
I recently procured what I believe to be a generic/chinese MID Tablet PC.
As far as I can tell, it's either a Rockchip 2918sdk or 2818sdk, or at least something similar.
It is a 7 inch tablet with power, volume up and down buttons. A headphone jack, HDMI port, USB connection, DC-5V charging port and a TF CARD slot for a micro SD Card. There is a camera on the front and a speaker on the back.
The label on the back states:
MODEL: 703H(B-2)
SOFTWARE: 4.04
POER:R-X-X-9-17
8GB
Click to expand...
Click to collapse
I was able to attain root but without thinking, I replaced the stock boot images/movies. Now when it boots, it forever continues to play the boot movie.
I gained entry to the stock recovery which is labeled "Android system recovery <3e>" "Recovery system v4.01"
With the volume keys and power button I can choose any of the seven options, yet none seem to help my boot loop issue.
The options include:
reboot system now
apply update from external storage
wipe date/factory reset
wipe cache partition
apply update from cache
recovery system from backup
update rkimage from /sdcard
Click to expand...
Click to collapse
The ways in which I believe I could repair the system are as follows.
1. Somehow access the onboard system memory with a file manager or through some other method, then delete the bootup/shutdown image movies.
2. Us and update script written and designed to delete these bootup movies from the recovery/flash menu (which I would have no idea how to accomplish)
3. Flash a original firmware image, (which I do not have)
Any ideas are welcome, thanks for your help!
Related
I searched the forums, and didn't see an easy to follow answer to my question.
I just got one of the woot tablets, so I've only had it a few days. It is stock, but I did temp root it so I could apply the market fix. Everything was working fine for a couple of days, but this morning when I turned it on, it seemed to be in a boot loop (the Tap N Tap screen kept cycling until it shut itself off).
Will I need a micro sd card to recover? I saw some threads that talked about connecting to a computer and transferring a file to the internal drive, but my computer isn't recognizing the internal drive on my g-tab. I can only see it when the G-tab is booted up, and I turn on the USB transfer from the G-tab.
If there is already a thread with easy to follow instructions could someone point me in the right direction?
BTW, I have already tried the vol+ and power button, I get the message that says recovery key detected, and then the box in the center of the screen. but then it continues into a boot loop.
Thanks for your help.
LisaBham said:
I searched the forums, and didn't see an easy to follow answer to my question.
I just got one of the woot tablets, so I've only had it a few days. It is stock, but I did temp root it so I could apply the market fix. Everything was working fine for a couple of days, but this morning when I turned it on, it seemed to be in a boot loop (the Tap N Tap screen kept cycling until it shut itself off).
Will I need a micro sd card to recover? I saw some threads that talked about connecting to a computer and transferring a file to the internal drive, but my computer isn't recognizing the internal drive on my g-tab. I can only see it when the G-tab is booted up, and I turn on the USB transfer from the G-tab.
If there is already a thread with easy to follow instructions could someone point me in the right direction?
BTW, I have already tried the vol+ and power button, I get the message that says recovery key detected, and then the box in the center of the screen. but then it continues into a boot loop.
Thanks for your help.
Click to expand...
Click to collapse
You probably need to do the NVFlash to stock ROM.
Well.. I'll throw my idea out there.
I think you may need to re-partition the SD card.
Apparently this happens to all of them at some point, and in fact it did happen to mine.
The device comes rooted, so you aren't rooting or unrooting in any of this. Its already rooted.
Go here: (the clockwork guide)
http://forum.xda-developers.com/showthread.php?t=865245
You'll want to download the cwmod_microsd from the first post, then extract the zip to the root of a micro sd card. Put the microSD card into the tab, then boot using the Vol+ and power. You will get the message that a recovery key was pressed then its going to automatically install clockworkmod recovery.
I dont recall if it finished booting at that point or shuts itself down. Regardless you'll still be in your bootloop so start it back up again using the vol+ and power key again.
This time you'll be greeted with clockwork recovery.
Once in the menu, you can go to Advanced and mount the sd card. Copy any files off of it that you may need to your computer, the next step will erase the internal SD card.
If nothing is needed, ignore this step.
**I repeat, the internal SD card will be wiped here.
From within clockwork mod recovery go to Advanced->Partition SD card. Choose 2048 for the first option and 0 for the swap.
Go back to the main clockwork screen and choose to restart device.
Cross your fingers that you boot up without a loop.
I'm doing this from memory, so if my verbage is a little off my bad. But you should see what I'm talking about.
Thank you... So I guess I need to go out and buy a micro sd card. Any size/class recomendations?
Depends.. Do you want it to get it back up and running.. 1gb or less.
Or do you want to also increase the storage of the device.. 4-32gb recommended.
If you just wanna get rolling again then get whatever the cheapest one available is.
If you're going to continue to use it, try and get a class 4 card or better, it will help with bigger file transfers.
LisaBham,
Yes, you probably will need a microSD card and it's good to get one that comes with an adapter so it fits in a SD slot to read/write. Also, if your computer does not have
a built-in reader that reads micro- or SD cards, you might need an adapter to USB.
Main thing is that you have two options, it looks like to me:
1. If you have a microSD card, you can make a CWM Recovery card out of it. Then
you can possible load CWM and get it to work even though you at looping (and BTW,
that's not your fault -- G-Tabs just do that one in a while.):
http://forum.xda-developers.com/showthread.php?t=1020747
If you can get CWM loaded and up, go to Advanced and run the Partition (2048 and 0)
option and the Fix Permissions Option and the Wipe Dalvik Cache option. Then go back to the Main Menu and run the Wipe Cache and Wipe/Reset Factory Data.
The shut down, boot and see if the G-Tablet will come up and work.
2. If one doesn't fix the looping problem, then you will need to continue and nvflash
back to a fresh, stock copy of the os.
http://forum.xda-developers.com/showthread.php?t=861950
If you follow this thread all the way through, it installs a copy of bekit 1105 which is stock version 2638. Assuming that boots and runs, the when you hook up the wifi
connection it shortly will offer you an OTA (over the air) upgrade to 3588. Then
you are back to where you can do what you want to.
Hope this helps.
Rev
So I may have bricked my phone because yes, I am an idiot.
Here's how I bricked it:
Pre-stuff: I downloaded ROM Manager on my newly rooted phone and installed Clockwork Recovery. My device wasn't supported, so I had to use one of the "Other models" options and it installed fine from the looks of it.
1. I was going to flash it to Xquizit 6.1, so I put the Superwipe and the rom itself on the phone's internal memory.
2. I went into recovery. I was given 4 options;
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
install fota
3. I went to apply update from sdcard and was told to use the Superwipe. Well me not reading it correctly, apparently this was supposed to be done via an external SD card. Not the internal memory. So basically I'm assuming it got rid of every single trace of the actual operating system.
4. Mistake #2: I misread the Superwipe instructions thinking it already made a Nandroid backup for me (I have no idea what that is or how to make one) so I figured I was fine.
5. Now when my phone boots up without me pressing extra buttons, it goes to the Samsung splash screen and then the Exhibit II 4G splash screen for a long period of time before turning off, restarting, and doing it over again.
6. I was told that I should have used an external SD card, so I went out and bought a micro SD card + a USB card reader so I could put files on it. I put the Xquizit 6.1 rom on the micro SD card, but low and behold, I go into recovery and go into my file tree, find external_sd only to see that the only folder on said external_sd was an empty DCIM folder...
So heres some basic info:
When I hold Up + Power button, it will boot into the same recovery. I get 4 options, as mentioned above. No option to mount the SD card, no place to view the contents of the SD card. None of the options are any use to me right now except "apply update from sdcard". One problem though, since (I think) it's the internal memory, when I go to try and flash my rom through there I get an error:
Code:
-- Install /sdcard ...
E: Short write of /tmp/sideload/package.zip (No s
pace left on device)
Installation aborted.
When I hold Down + Power button, it takes me to a warning screen that says "A custom OS can cause critical problems in a phone and installed applications. If you want to download a custom OS, please press the volume up key. Otherwise, press the volume down key to cancel." When I press volume up, it takes me to a screen that says Odin Mode, has a lil bit of info in the upper right, and has the Android logo along with "Downloading... do not turn off target!!"
Except I left it on this all night and it didn't do anything...(probably a noob thing to say).
When I hold Up AND Down + Power button, it takes me to the ramdump screen.
So far from all my Googling I can't seem to find people who have had the same issues as me. Any idea on what I can do? Much thanks in advance.
cant find the delete button
anyways the device is fully hardware bricked.
it was a 1.4.2 oem off the shelf nook
it showed rev3 for the omap processor
thats pretty much all the hardware details i remember:
How i permanently bricked it:
after having Lag0matic help me i recovered the 1st time i soft bricked it by using adb to wipe the mmcmlk0 memory card, then re-partition it.
i used the ubuntu wipe and restore image to flash back to 1.4.0 that is included with the ubuntu tool
i rebooted the device and skipped registration and made sure it worked
i used sdformatter to wipe a 16bg pny card i bought from walmart (it is a 4 rated speed card)
i placed the 8-16gb cwm extracted files from the 8-16 cm7 recovery img to the card
i placed the teamb-beta-1 zip onto the card
i placed gapps onto the card
i then booted off the SD card with the cm7 recovery image and installed the teamb-beta1 zip successfully
i factory wiped as recommended
i cleared the cache as recommended
i cleared the dalvik cache
i then installed gapps via the same way
i removed the sd card
rebooted
installed some video players (pretty much all of them that had more than 4.5 stars to try play HD video
it woudlnt play hd video
noticed the hardware players would not enable hardware codecs, and if forced would hard lock the thread and force me to hard boot it
gave up on that, copied some games from my htc-glacier over to my sd card for the nook (i copied the whole sd card from the phone)
played some games but the saved games would not load
copied them to the internal "sd card" (data space)
still would not load saved games
figured to clean install it again
using the normal memory card manager (NOT that evil tophat rommanager) i formatted the sd-card, and the internal card by dis-mounting them then formatting them
made the cwm bootable, added the rom and gapps again (same versions)
...
device will not boot with the cable plugged in
unplugged the cable, it boots, but the memory card will not boot the device. it locks up on the "non animated" boot screen
plug the cable back in, still wont boot from it
take out memory card
now it boots with the cable plugged in. wierd. oh well. put stick in and hit the N button to load the recovery manually
recovery will not load from the sd card. "bad image, crc etc"
/huh i think/
reboot again, no sd card, hit n to go to the internal recovery
internal recovery loads, shows me the same errors as before indicating the partitions are gone ... again ....
/me = scream and swear .... alot
go to recovery
recovery cannot write to data, system. emmc, only boot AAAAND! it no longer says happy errors, now it says omap.c can't mkfs on .... blah (alot of things)
/me = oh ****, it is referring to itself as the cpu... not a good sign/
fire up adb
adb shell = no devices
/me = no biggie/
stop and restart adb kill/start server like last time to pick the unit up
adb devices = ur boned dude..... no devices
/me = ooooohhh ****/
look in device manager
the generic adb device entry ... is not listed...
/crap self/
re-install windows to seperate box
adb still wont see it
reboot issues are getting worse... now it keeps doing the soft-recovery for BN.... then hanging.
/DURP/
after that last reboot and "self heal attempt" it is fully durped.
it will not boot if the usb cable has power to it, be it computer or wall plug
it will not boot from the sd card. and 50% of the time with the sd card in it wont power at all.
by not powering up, the lcd stays dead, no flicker, no backlight so this is not a blank screen, or hung.
so. the unit may be defective... not sure. but theres my story. and a big note of warning.
thank you mega,Lag and others... but i think the unit is going back, and i think im opting for a refund. i learned alot, but the device just makes me feel uneasy in its current state. maybe i will pick a used one up when cm9 hits stable beta, but cm7 was excellent but as i discovered not quite enough (video playback, i did not realize that gingerbread had issues with mkv which is 99% of my video collection).
I bought a cheap A-13 MID of the internet and flashed a firmware for another variant common problem with these devices so i have no touchscreen and the usb has snapped of tried soldering it but was unsuccessful
I have recovery installed but only way i can use it is through novotools but need touch screen
So i need a way to flash firmware through sdcard on boot (Can be done, can't find guide though)
Or a script that will run reboot-recovery.sh on boot from sd or maybe emmc
Or that will run when the sd is mounted so that if i insert an sd card into the device with reboot-recovery.sh script on it it will reboot to recovery
Must be a way to fix this
Neurom707 said:
I bought a cheap A-13 MID of the internet and flashed a firmware for another variant common problem with these devices so i have no touchscreen and the usb has snapped of tried soldering it but was unsuccessful
I have recovery installed but only way i can use it is through novotools but need touch screen
So i need a way to flash firmware through sdcard on boot (Can be done, can't find guide though)
Or a script that will run reboot-recovery.sh on boot from sd or maybe emmc
Or that will run when the sd is mounted so that if i insert an sd card into the device with reboot-recovery.sh script on it it will reboot to recovery
Must be a way to fix this
Click to expand...
Click to collapse
Uppp
I have a weird one. I have rebuilt my Nook and followed the directions about how to make the SDcard active, the flag is correct and everything. It will load the loader if I power it on via a powered USB cable but when I try to power it off and back on without the cable, it goes directly into the original nook tablet OS. Any suggestions on how to fix this issue?
flyboynm said:
I have a weird one. I have rebuilt my Nook and followed the directions about how to make the SDcard active, the flag is correct and everything. It will load the loader if I power it on via a powered USB cable but when I try to power it off and back on without the cable, it goes directly into the original nook tablet OS. Any suggestions on how to fix this issue?
Click to expand...
Click to collapse
You're not the only one. This seems to be a common issue between newer (or was it older?) model Nooks.
sagirfahmid3 said:
You're not the only one. This seems to be a common issue between newer (or was it older?) model Nooks.
Click to expand...
Click to collapse
On my previous build - Cyanomod 10 - Jelly Bean, I didn't have this issue. I just lost that memory card and tried it again and get the boot issue.
flyboynm said:
On my previous build - Cyanomod 10 - Jelly Bean, I didn't have this issue. I just lost that memory card and tried it again and get the boot issue.
Click to expand...
Click to collapse
now it seems u know the steps already but im reposting in case u missed something.....i had the same problem. i found that some NT's only respond to this exact file that i will provide. use my files in this step and get back to me. REMEMBER TO READ ALL STEPS I PROVIDED IN CASE U FORGOT SOMETHING
step1- download (https://www.mediafire.com/folder/dd1cwv3uw0u18/NOOK TABLET) <<-----sdboot.zip and cwm.zip
step2-download minitool partition wizzy
step3-put sd card into computer
step4-using minitool, delete partition, create partition (make primary, and fat32), right click on sd card (usually F set flag to active and change partition ID type to 0x0c fat32lba and then click apply. (IN THAT ORDER)
step5-once parted copy from the sdboot attatchment provided to sd card, the recovery.img, MLO,flashing_boot, and u-boot. Also put the cwm emmc.zip provided as well into sdcard.
step6-put sd into nook, MAKE SURE NOOK OFF BEFORE U PUT IT IN OR U WILL HAVE TO DO IT ALL OVER AGAIN, then plug nook into computer via usb cord, be patient and wait for nook to boot, once it finally boots, U MUST BE VERY QUICK AND PRESS "N" THE SECOND CYANOBOOT POPS UP, GO TO SDC RECOVERY NOT INTERNAL RECOVERY. that will load up sd cwm, once it is up it will now let u install the cwm i provided. install it.
step7-once this is done unplug it from comp, turn off, and repeat steps 3-6 (BUT THIS TIME ADD THE CYANOGENMOD 10.+ YOU WANT TO USE IN THE SD CARD AS WELL ALONG WITH THE CORRECT GAPPS) once sd cyanoboot pops up choose internal recovery instead of sdc recovery. install cm10+, gapps, and the internal cwm emmc.zip i gave u as well for good measure.
step8- once done take out sd card and reboot regularly with/without usb doesnt matter. u should be good...........it seems like alot but its actually rly fast when u got the hang of it.