Got a brick. I can not get into the APX mode.
Hold down Volume (-) and power while booting - did not work. May have other options?
That should be volume (+) and power.
Sent from my UPC300-2.2 using Tapatalk
SgtJake said:
That should be volume (+) and power.
Sent from my UPC300-2.2 using Tapatalk
Click to expand...
Click to collapse
Thank's no work recovery
Does not react not to what combination of buttons. What do I do need help.
I download and install
tegra_froyo_20101105.
And ran nvflash_1gb_crt_256VRAM.bat
"nvflash.exe" --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x3c300011 --create --go
@set /p batuserinput=Press enter to continue:
Click to expand...
Click to collapse
Now my MALATA not that does not respond.
Haltol - APX mode is just a blank screen. You won't see anything unless your APX drivers are working on your PC and NVFlash is able to talk to the G Tablet. It's also not clear from your posts if you have a G Tablet or a ZPad - they are slightly different in terms of partition table structure - need to find somebody with a ZPad to tell you more about nvflashing one, or search the forum.
What happens when you press Vol - while booting? Blank screen? What happens when you try to run nvflash? Do you get any message, or nothing at all? We need a bit more info to help...
rcgabriel said:
Haltol - APX mode is just a blank screen. You won't see anything unless your APX drivers are working on your PC and NVFlash is able to talk to the G Tablet. It's also not clear from your posts if you have a G Tablet or a ZPad - they are slightly different in terms of partition table structure - need to find somebody with a ZPad to tell you more about nvflashing one, or search the forum.
What happens when you press Vol - while booting? Blank screen? What happens when you try to run nvflash? Do you get any message, or nothing at all? We need a bit more info to help...
Click to expand...
Click to collapse
I have ZPAD.
When any combination of buttons a black screen.
Nvflash
Nvflash started
USB device not started.
Click to expand...
Click to collapse
Drivers are installed, before everything worked. I can not get into the mode APX
You ran an incorrect file. The one you ran directs the tablet to output to a crt for debugging as the included .bat or .sh files are for the developer boards.
I do not know what or how you can fix this this.....all output is now being directed to a monitor that your tablet doenst have physical comnectors for.
Sent from my Viewsonic 10" GTab...
HELP!!!!!!
You're right. And what do I do now? Is a brick? And there are not any options?
this part ( --odmdata 0x3c300011 ) is the settings I believe for changing pieces in the BCT. You would need to research what the proper one is......and use the correct flash.bct and flash.bct files with the correct --odmdata command.
I believe this is what toasted one of mine...I can still boot (by forcing it with nvflash), I just can't turn it off or it will not turn back on until I nvflash it again. I don't remember what I used but I do remember the --odmdata being in it...I just don't know the correct bits to push.
I have nothing I can do. Not included. not loaded rekavery. No load mode. I do not know what to do. Any ideas?
From this page: http://tosh-ac100.wetpaint.com/page/Bootloader
"There is more dangerous command called --odmdata. It is some kind of fingerprint of the hardware and
enabled/disables certain hardware configuations. For example, the ODM 0x3b2d8011 data causes the HDMI port
to be used for bootloader display."
So you probably haven't bricked the tablet, but like tcrews suggested, you've pushed a command that has likely redirected the bootloader display output somewhere else.
According to the page linked above (which is for the Folio 100, another Tegra 2 tablet, but I assume the basic gist is the same?), bits 20-22 of the odmdata command control the display output of the bootloader. Not sure if that applies to the ZPad.
The real question is what is the default odmdata configuration for the ZPad, and if you push that in APX mode will you get back to normal bootloader function again (I'm guessing yes).
You might start by downloading the proper nvflash stuff for the ZPad:
http://www.ez-pad.net/android-1340-1-1.html The page is in Chinese, but apparently the links there point to the nvflash packages for the original ZPad.
According to that page, the odmdata setting should be something like 0xba0c0011 for the ZPad.
So... try downloading those packages I linked to, see if you can flash them from APX mode, make sure that they are sending an odmdata setting (if you don't see one in the batch file, maybe try the one I just read off of that page).
Let us know if you have any success with this...
Thanks guys. But there is a problem I can not get into the APX mode.
I can not perform any commands as the device is not detected.
Colibri Recovery Mode
I think I found something interesting if we built on Colibri
Colibri Recovery Mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tomorrow I will try to run mode APX
x2 on "--odmdata 0xba0c0011". That should be for zPad.
If you can get APX working again, then that should "fix" it I think. Suggestion: If you have an *nix box, keep trying this command:
lsusb
You want the Nvidia connection to have a "7820" (that means APX mode). This helps if you have no boot screen and you are just trying buttons blindly to get into APX.
Hi,
Sorry for jumping in, but it sounds like the OP tried to nvflash the stuff from the 'generic' Nvidia Sdk to his Gtab? Maybe I'm misreading/misunderstanding, but if he did try to flash the Nvidia Sdk files, would anyone have expected that to work?
I mean that that has a different (non-Gtab, non-Malata) .bct, partition table, partition files, etc.?
Maybe I'm just confused...
Jim
Jim - correct - he flashed some crazy stuff onto his ZPad.
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
I can not get the APX mode
I can not get the APX mode.
I'm in the hands of a brick. I do not know what to do. Help if anyone knows.
Are you positive that the device is not going into APX mode, you just can't tell?
On mine....the only way I can tell is to watch the activity of the USB port (either in Win764 or Ubuntu 10.04 (Virtual Box). Once the USB icon shows some activity I can nvflash. My device shows nothing on screen until I push the bootloader.bin over. No power flash, flicker, anything......
Just making sure you are checking your connection and using the proper key-sequence to boot to APX and not just watching your tablets screen.
haltol said:
I can not get the APX mode.
I'm in the hands of a brick. I do not know what to do. Help if anyone knows.
Click to expand...
Click to collapse
Hey Roebeet...any idea what the default --odmdata is for the Viewsonic?
roebeet said:
x2 on "--odmdata 0xba0c0011". That should be for zPad.
Click to expand...
Click to collapse
tcrews said:
Hey Roebeet...any idea what the default --odmdata is for the Viewsonic?
Click to expand...
Click to collapse
Hi,
I can't find the link right now, but I seem to recall from one of the threads on the wetpaint.com website that someone had used --odmdata and inadverdently borked their .bct (BCT). I think that he said that he had looked at the BCT afterwards and found that the byte sequence (reversed-ordered maybe) that he had used in the --odmdata appeared at the end or beginning new BCT afterwards, so he hex-edited the new .bct then did a --setbct with the hex-edited .bct.
In other words, at least what I recall, the hex sequence in the --odmdata gets flashed somewhere into the BCT, so maybe do a --getbct on a working Gtab, and look at the resulting 4080 byte file with a hex editor?
I'll try to see if I can find the link later. Sorry.
Jim
Related
I don't understand how to use it :\
I've been browsing the forums and reading posts all day long, but I can't seem to get this.
I am sure my lumia has an unlocked bootloader since windows asks me to format it when I test it.
Here are some info about my thing if it helps.
location of the rom I am trying to flash: C:\Users\David\Desktop\os-new.nb
location of dd.exe: C:\Users\David\Desktop\os-new.nb
drive letter of the phone : E:
When ever I command dd to do "dd if=./os-new.nb of=/dev/sdE9", replaced "x" with the drive letter of the phone which is E.
It doesn't seem to do anything, or it doesn't do anything at all...
Can someone do a detailed tut for this; in windows? I'm not a noob by any sort but this is just frustrating with such limited instructions.
looks like no one is kind enough to clarify. Ok.
Sent from my Lumia 710 using Board Express
You cannot use dd on windows; it's an internal Linux command that doesn't exist in Windows.
Hmm, why did it say we can use the windows version of dd?
Sent from my Lumia 710 using Board Express
If so then is it possible to flash the .nb with Qualcomm qpst? I don't have enough diskspace to install linux
Sent from my Lumia 710 using Board Express
wndows version of dd may no use, and i don't konw why
dd is used to copy the nb file to disk?
maybe another software to do like this, such as winhex?
dewe said:
wndows version of dd may no use, and i don't konw why
dd is used to copy the nb file to disk?
maybe another software to do like this, such as winhex?
Click to expand...
Click to collapse
I'm trying it again with DD in linux this time. Took a hard drive out of a broken ps3 and installing ubuntu on that
If you don't want to install Linux on a separate hard drive or partition, Cygwin is your friend. Be sure not to accidentally dd erase your Windows hard drive though...
Refrain from use of Windows to unlock bootloader, most likely to brick your device, use Linux, if you don't have it, don't try it. You have been warned.
sHaHiN786 said:
Refrain from use of Windows to unlock bootloader, most likely to brick your device, use Linux, if you don't have it, don't try it. You have been warned.
Click to expand...
Click to collapse
Hmm, can you give me a step by step instruction to do this?
I went from the Nokia DLOAD to Qualcomm loader already. Thats how far I am. I've also played around with the DD commands with my uncles mac.
dd if=./os-new.nb of=/dev/sdX9
if the phone shows up as /dev/sdb3 on ubuntu, do I do
dd if=<path to the .nb>/os-new.nb of=/dev/sdb3?
wardoc22 said:
dd if=./os-new.nb of=/dev/sdX9
if the phone shows up as /dev/sdb3 on ubuntu, do I do
dd if=<path to the .nb>/os-new.nb of=/dev/sdb3?
Click to expand...
Click to collapse
dd if=./os-new.nb of=/dev/sdX9
Where X is the disk detected by your linux distribution.
After that, you'll need to hard reset the phone. Hold Power button for 10 seconds to exit Qualcomm's disk mode, and press and hold POWER+VOLUMEDOWN+CAMERA until you feel the phone vibrate. After that, RELEASE power button but KEEP HOLDING volume down + camera for five or more seconds. This will trigger the hard reset.
sHaHiN786 said:
dd if=./os-new.nb of=/dev/sdX9
Where X is the disk detected by your linux distribution.
After that, you'll need to hard reset the phone. Hold Power button for 10 seconds to exit Qualcomm's disk mode, and press and hold POWER+VOLUMEDOWN+CAMERA until you feel the phone vibrate. After that, RELEASE power button but KEEP HOLDING volume down + camera for five or more seconds. This will trigger the hard reset.
Click to expand...
Click to collapse
dd if=/home/david/os-new.nb of=/dev/sdb9
I already did dd if=/home/david/os-new.nb of=/dev/sdb3
Well, I screwed up =\
Now it gets recognized in windows as qualcomm device, but it won't show up in ubuntu.
I made a full backup of it though.. You got any ideas?
Anyways in the end, I phoned tmobile up, they said they will send me a new one. I will be retrying this when I get that new lumia
sHaHiN786 said:
Refrain from use of Windows to unlock bootloader, most likely to brick your device, use Linux, if you don't have it, don't try it. You have been warned.
Click to expand...
Click to collapse
^ I tried it the other day, and it bricked. LOOOL. I recommend listening to this guy. I ended up having to get a replacement device, luckily came the next day. attempted again except used Wubi for ubuntu, and it worked fine. i got the interop unlocked tango for the lumia 710
sHaHiN786 said:
dd if=./os-new.nb of=/dev/sdX9
Where X is the disk detected by your linux distribution.
After that, you'll need to hard reset the phone. Hold Power button for 10 seconds to exit Qualcomm's disk mode, and press and hold POWER+VOLUMEDOWN+CAMERA until you feel the phone vibrate. After that, RELEASE power button but KEEP HOLDING volume down + camera for five or more seconds. This will trigger the hard reset.
Click to expand...
Click to collapse
Lumia 710 does not support SW by pressing POWER button!
wardoc22 said:
dd if=/home/david/os-new.nb of=/dev/sdb9
I already did dd if=/home/david/os-new.nb of=/dev/sdb3
Well, I screwed up =\
Now it gets recognized in windows as qualcomm device, but it won't show up in ubuntu.
I made a full backup of it though.. You got any ideas?
Anyways in the end, I phoned tmobile up, they said they will send me a new one. I will be retrying this when I get that new lumia
Click to expand...
Click to collapse
Yeah, I guess you're pretty much screwed now. I don't get why people without a understanding of the DD command use it. Either way this procedure is still far away from being stable. You could try to reflash the third Partition if you have a backup somewhere. But if you don't you can only get a replacment device.
ChrisKringel said:
Yeah, I guess you're pretty much screwed now. I don't get why people without a understanding of the DD command use it. Either way this procedure is still far away from being stable. You could try to reflash the third Partition if you have a backup somewhere. But if you don't you can only get a replacment device.
Click to expand...
Click to collapse
Well I do have an understanding of what the command is and what every part of it means now... We learn from experience lol. I never had a huge experience with linux haha.
I will try to explain this as best as I can, to make sure I am correct, and to try to clarify the command for other people confused.
dd if=./os-new.nb of=/dev/sdX9
"if=./os-new.nb"
This specifies the file path of where your os-new.nb file is. So for example, the location of my .nb file is:
"/home/david/os-new.nb" so I would do "if=/home/david/os-new.nb"
of=/dev/sdX9
This specify the location of where you are copying the .nb file to.
For this, you would just have to replace the "X", and only the X, which is in terms of the letter your device turns up in linux as. This was the part I got confused on. It showed up as sdb3 on my machine, which I thought that I would have to replace the entire sdx9 with it.
To find out the letter, in terminal, type in
"df"
It will lists all your active drives. Mine shows up as the latter B, under the name windows device. So I would do
"of=/dev/sdb9"
So to put it all together, the command I would type in is:
"dd if=/home/david/os-new.nb of=/dev/sdb9"
Am I correct?
And also, if there a way to flash your lumia from within windows? Cause it still shows up as a USB drive in windows like usual but it refuses to show up in ubuntu.
And also, I gave up trying to make it show up on ubuntu and tried it on my uncle's mac.
Heres what I got.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I flashed the wrong partition, which was partition 3. So I am wondering if anyone can make an IMG file for partition 3 for me(lumia 710, unlocked qualcomm bootloader) then might be able recover it.
Worth a shot I guess as I will be getting a new lumia anyways.. And I might not have to be stuck with no phone for 10 days lol.
Stuck with a enterprise managed Chromebook bought second hand and unable to remove it? Here is how to 'Remove Enterprise Enrollment' from Acer C720 Chromebook (and will work for others also)
The procedure is as follows (for a Acer C 720 Chromebook) however it is the exact same for most other models the only differing part is location of the read/write screw.
Step 1: Turn off Chromebook, unplug and remove all the screws from the base.
Step 2: Remove the base off and locate the read/write protection screw
Here it is on the C720 at location 7:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 3: Screw the base on with one screw (because there is a pressure switch that won't let you start it up without having the base on)
Step 4: Plug in and go into Recovery mode (Hold Esc + Reload and press the power key). Release keys when you see the screen light up.
You'll see "Chrome OS is missing or damaged" screen
Step 5: Press Ctrl + D then enter
You'll see "Chrome OS verification is turned off"
Step 6: Press Ctrl + D and the CB will restart into developer mode.
Note: If it tells you administrator has disabled developer mode perform a hard reset by unplugging the battery internally in the device, disconnecting the power and holding down the power button for 60 seconds.
Step 7: Once in developer mode (it'll give you a warning screen then continue to boot up as usual after a few beeps) Press the keys Ctrl+Alt+-> (F2) to launch terminal
Step 8: Enter the following commands:
chronos
sudo su
vpd -l (display serial number and device info)
vpd -s “serial_number”=”0000000000X” (write serial #, can replace 0000000000X with anything you like) must be all CAPS and numbers.
(takes about 15 seconds)
vpd -l (to check change is successful as it doesn't give you any confirmation)
Step 9: Reassemble with all screws incl read/write. Reboot and turn OS verification back on.
Step 10: Enjoy your non enterprise enrolled C720 (or other) chromebook.
Step ?: (optional if you are getting error flashromPartialWrite() clean the contacts that were under the screw with isopropyl alcohol or meths to make sure there is no continuity between the points from wear.
** Note: I am not responsible for you damaging your device in any way **
If i've helped you in any way feel free to donate via the following button. Cheers
i need a little help i have the Samsung Google Chromebook XE303 XE303C12-A01U after trying to change the serial number when i go to check it with vpd -l it gives me the flashrompartialwrite() error. i checked and cleaned where the screw goes but i still get the error. is the screw supposed to be back in at this part of it? please help thank you
I get a login and password need help noob please
Smoker90 said:
i need a little help i have the Samsung Google Chromebook XE303 XE303C12-A01U after trying to change the serial number when i go to check it with vpd -l it gives me the flashrompartialwrite() error. i checked and cleaned where the screw goes but i still get the error. is the screw supposed to be back in at this part of it? please help thank you
Click to expand...
Click to collapse
I'm going to answer this a bit late in case anyone else has this question...
The R/W screw needs to be off until you are ready to put your laptop back together. (after all, you want to be able to write to bios and the screw in place will prevent this)
Doesn't work
hOW CAN YOU REMOVE THE ENTERPRISE ENROLLMENT FROM AN ACER C910
How do you do that on a c730
Version 5.4
Here I am in 2017 will be trying this on a c740 in the near future. Thank you for the guide
is this possible on a hp chromebook 11 g4, if so wher eis the read/write screw located?
I cant't get the administrator has disabled developer mode page. I have tried removing the battery as suggested and had no success.
Same!! Trying soo hard to find a solution
So, I have a Toshiba Chromebook 2. I found it has 2 screws for write protection. Removed them both, no change, I still get the developer mode disabled by the administrator message. Can`t do anything on it. Is there a custom OS I can install over the existing one so I can at least get developer mode enabled?
I have an Acer C731. I opened it up and tried to do a hard reset by unplugging the battery, with no luck. As soon as the Chromebook was connected to Wi-Fi it enrolled under administration. I also was not able to locate the R/W screw in this particular model. Help please?
jbywater said:
I have an Acer C731. I opened it up and tried to do a hard reset by unplugging the battery, with no luck. As soon as the Chromebook was connected to Wi-Fi it enrolled under administration. I also was not able to locate the R/W screw in this particular model. Help please?
Click to expand...
Click to collapse
The screw is located near the wifi card with a white arrow.
josuecas said:
The screw is located near the wifi card with a white arrow.
Click to expand...
Click to collapse
Yes on my Asus CN60 chromebox, the r/w screw is screwed onto the motherboard, onto a solder pad that is a semi-circle split into two quadrants. The presence of the screw joins the two quadrants to emulate a PC jumper in the closed position.
To open this jumper, simply undo the screw all the way out and keep it safe outside of the box. Once this is done, the boot SSD is r/w, which then allows the developer mode process be able to commit its changes to the boot device.
On my Asus CN60, I think I have cleared the Enterprise enrolement by having the two items present whilst doing the power on with Recovery Button pressed.
- R/W screw removed.
- CMOS battery CR-2025 unplugged.
I am going to keep trialing. If the above has not worked, I am going to try the OP's vpd -s “serial_number”=”0000000000X” method.
ASIDE: I am going to keep a note of the serial number I am overwriting in case this is of any future use.
The reason why I say I think I have removed the enterprise enrolement, is before, I could not login at all. Now, whilst in the developer mode, I can now login using my normal non enterprise login.
I have yet to boot into a normal non developer mode if possible, and see if I can login there.
I've bypassed enterprise enrollment so I can login and use the chromebook normally, but I wasn't able to locate the r/w screw so I can move forward with installing Linux.
RyanPieper said:
I've bypassed enterprise enrollment so I can login and use the chromebook normally, but I wasn't able to locate the r/w screw so I can move forward with installing Linux.
Click to expand...
Click to collapse
how did you go about getting past the "administrator has disabled developer mode" part, or did you have to? i am stuck on that part.
I have an HP Chromebook 14 G4 and followed the tutorial perfectly. I still can't get past the "The administrator has disabled developer mode" bs. Any help?
Request
Can you please make a guide on how to do this with an acer c740 with specifucs on how to do so if the administrator has disabled dev mode?
C732
How do I unenroll an acer C732 with dev mode blocked?
does this still work?
This is the stock Rom of N & M for Yoga Book LTE & WIFI for the needers
if any dev want to help me developing a dual boot for Yoga Book, just PM me or join Telegram Group for Yoga Book devs and users:
MOD EDIT: LINK REMOVED
Prees the Thanks button if that helps you
How to install it:
Be careful, these steps will erase all your data on tablet and will downgrade rom (stock marshmallow)
First of all: read and understand all of the instructions.
1. Download the stock ROM
https://cloud.kolyandex.su/index.php/s/4WDt6ghOzHAyP4s (Nougat WiFi version)
https://easy-firmware.com/home/browse/category/id/19521/ (Marshmallo LTE version)
https://androidfilehost.com/?fid=817550096634799507 (Marshmallo WiFi version)
2. Extract it to some folder
3. Download Intel Platform Tool Lite from here: https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
4. Install Intel Platform Tool Lite
4. Boot into fastboot mode
5. Run Intel Platform Tool Lite
6. Make sure your tablet is recognized by the tool (otherwise you need to enable USB-debug in Developer settings)
7. Select "flash_update_from_eng.json" from folder in (2)
8. Push "start to flash"
9. Wait... (You should check tablet's screen in order to lock/unlock bootloader (it should be locked after flash in order to install OTA updates))
10. Reboot tablet
11. Your keyboard might not work: that is normal (just use on-screen keyboard for now)
12. After initial setup: open Contacts app, create new one (if there are no contacts yet), tap search and enter ####6020#
13. Choose your region
14. Reboot
15. Setup again (now halo should work)
16. Go into settings -> about -> updates and update till the last version (may take several hours)
17. Say thanks for alexjustes for his Amazing Steps
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
beltani said:
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
Click to expand...
Click to collapse
Unfort. no, because i dont have a YB Android Version, i have win ver.
THE MAXIMUM POWER said:
Unfort. no, because i dont have a YB Android Version, i have win ver.
Click to expand...
Click to collapse
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
beltani said:
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
Click to expand...
Click to collapse
Same, it can only flashed through fastboot mode
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
@MarkAllen, thank you for your valuable information. This will help people unbrick their devices.
MarkAllen said:
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
Click to expand...
Click to collapse
Thank You for the INFOS
The tool does not recognized my device
Please help to flash my yoga book.
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
jeitana said:
Please help to flash my yoga book.
Click to expand...
Click to collapse
Try installing Android SDK drivers in you PC
Guys, if anyone faced a Probleme during his way to flash the ROM, PLZ tell me the problems with More Details
_Deeb0_ said:
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
Click to expand...
Click to collapse
Is this compatible with the Yoga Book A12?
I have been away for a while. Why should I want to install this rom?
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Shawnki91 said:
Is this compatible with the Yoga Book A12?
Click to expand...
Click to collapse
Sorry but no
hajkan said:
I have been away for a while. Why should I want to install this rom?
Click to expand...
Click to collapse
No Need to reinstall this Rom if you have already your System, both are 100 % same
hajkan said:
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Click to expand...
Click to collapse
Reinstall the Rom will fix this, but doing factory reset will fix this too
In case anyone wants the wifi only M firmware here it is https://androidfilehost.com/?fid=817550096634799507
Hey All
Its been a while since I got to play with anything these days but I recently found one of these POS 10in touchscreen units in the dumpster and it fires up into a menu running android. So I was hoping I could reflash this and use it like a tablet given it's also got a small thermal printer in it, so maybe try and save it from e-waste
I searched online for more details and came across this HERE which is identical to what I have so hoping I can root it and flash it with a clean android?
I would love to repurposed this to use as a touch screen tablet or similar, since it's got a GSM module and can take an SDCard too as I opened it up and took some pictures and I managed to get it in a recovery mode as well - from the PIX its using a rockchip RK3368
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am not sure if the mini usb port is a OTG port to try and use ADB but I have not been able to do much with it and hoping someone can guide me through to possibly a reflash or ways to unlook root and add in another bootloader/rom
I've downloaded the files from citaq website but so far not been successful to do much with it, has anyone played with these and turned them into something more practical for the home?
Here's hoping for some tips - Apology if this is in the wrong section, move as needed :good:
Cheers
Kosti
@Kostiz
Device actually is running Android 5.1.1. It seems it has only 1GB RAM what is far too little to run a full fledged Android.
As long as you don't replace device's Stock Recovery by TWRP or similar recoveries, after a successful rooting don't install Magisk and/or Xposed Framework, you're on the safe side to play with, IMHO.
As 1st step check whether device is accessable by means of both ADB and Fastboot.
jwoegerbauer said:
@Kostiz
Device actually is running Android 5.1.1. It seems it has only 1GB RAM what is far too little to run a full fledged Android.
As long as you don't replace device's Stock Recovery by TWRP or similar recoveries, after a successful rooting don't install Magisk and/or Xposed Framework, you're on the safe side to play with, IMHO.
As 1st step check whether device is accessable by means of both ADB and Fastboot.
Click to expand...
Click to collapse
Hey, Thanks for chiming in!
So in order to get ADB and or Fastboot its suggested to enable USB debugging in the device system settings, but I am not sure on how to do this, would it be safe to assume this is already USB debug is already enabled?
Could I back up the original stock recovery
I'm a little green on the whole process hence looking thought I'd ask here, I don't think I even have an OTG cable handy
I will see if I can load ADB on a windows box and try and talk to this unit
Cheers
Kosti
@Kostiz
An OTG-cable isn't needed, because the recovery menu
doesn't give you the opportunity to load something from an USB-device
OK, some success!
I went back and connected a mini USB straight to the PC and ADB driver installed detected the android device.
Ran ADB in windows powershell
So whats the best method to backup the entire ROM, and recovery files in the event I stuff this up?
Do I use just ADB for this or someother tools?
I did try one tool here from the vendors website but stuck as not sure what the Chinese characters mean..
Is the fact that this is only 1G i couldn't run Android at all and needs to be stripped down?
Cheers
Kosti
@Kostiz
Android Oreo Go Edition is a lightweight distribution of Android that runs better than normal Android on devices with <= 1 GB of RAM
How to backup device's Stock ROM is eplained here.
Thanks again mate!
Seem I have to do a lot of reading and thankfully everything is here, just got to spend time to read and have a go!
BTW how do I go about using volume rockers and power button to move around the menu in recovery when there is none but only the two buttons as shown the reset and recovery buttons on the main board?
BTW, the current ROM installed boots into a special menu, all other settings are hidden, would there be a way to enable seeing all the items and when getting the the settings (gear icon) that pops up in the corner, only takes me to the standard wifi menu to choose a wifi, so it seems everything else is hidden, if by enabling these I could potentially not need to do anything other than stop the default application from starting up - if that makes any sense
Could I just get back into a adb shell and try
adb shell
su
pm enable applicationname
I have to read up on rooting first I assume before I do much more, this is getting exciting, LOL :good:
Kostiz said:
BTW how do I go about using volume rockers and power button to move around the menu in recovery when there is none but only the two buttons as shown the reset and recovery buttons on the main board?
Click to expand...
Click to collapse
You use Android's HOME button to navigate within the Recovery menu, use POWER button to select option.
Hi, fellas! Please help me with one of these Citaq H10 POS. All we have is bootloop with some custom ROM showing vendor's logo.
Forcing it into recovery gives me some dead android screen with "No command" text.
Please guide me through this challenge, cause I have no other option but to ressurect it somehow.
Good news is that I have another one that is working fine, so we could try cloning it or something. Please help!
Yet I can't attach pics, cause of few posts, but if needed I can PM some.
citaq h10-2
I am also stuck with this machine citaq h10-2 , i did use a wireless kb to move up/down and not the 2 buttons on the motherboard , i can talk with it with ADB but all you can do is put it in sideload to upload new firmware and put it in fastboot but in fastboot you only get a black screen , what I have don is > opened up developer mode but you have no OEM UNLOCK tick box in side so running any bootloader unlock dose not work and i have run them all, if you google this machine for flashing new firmware you only get XDA this forum, unless any body knows another place to get the info from please let us know as i do think this would make a nice tablet with printer, the firmware is 5.1.1 and would love to put 6.0 or above on it but. i did download some firmware and used sideload to install it but it come up with error , i did try and make a backup but cannot do it ?, I think the firmware was from a galaxy s5 , I am not into all this firmware flashing so I am learning as I go along and if I brick it up well it was for free any way as the takeaway was shutting down and he gave it to me so no loss, if any body knows how we can get 6.0 or above on this machine please let us know.
A big thank you to all that can help put android 6.0 or above on this tablet.
Did you guys take a look at the solution here ? It worked for me ! All with a 2k ohm resistor...
Hola, alguien tiene la Rom de este dispositivo?
Hello,
My phone felt down from the 6th floor through the elevator shaft, ending up really damaged: broken screen (fully black, top left corner partly chipped off) !
Yet, the phone is not completly dead:
- The alarm keeps ringing at each time I have scheduled (several each morning )
- I'm able to switch off the alarm by by swiping left through the bottom of the screen, or by pressing the on/off button
- when I plug phone to my PC (win10) I can hear the bip-bip typical of a device connection, but nothing else happens
- On a PC on which the phone had never been connected, Windows recognised the phone and installed the drivers, but again Windows doesn't ask me what to do with the phone
- bluetooth seems to be working as the phone is seen as available by other devices
I'm trying to find a solution to access some of the data in my phone. Primarily the DCIM folder.
I would like to reboot in fastboot mode, as I believe I may have USB debugging on.
However I don't seem to be able to switch off the phone or reboot it.
Any idea how I could switch off the phone? Enter fastboot.
Do you think I could access the phone screen using an OTG device plugged to my computer screen via HDMI. If yes, which OTG device should I purchase?
Any other idea?
As a last resort, do you think it is possible to fully ripp-off the phone, get the flash drive and mount it somewhere in a tool that could be pluggin via USB?
Surfinette said:
Hello,
My phone felt down from the 6th floor through the elevator shaft, ending up really damaged: broken screen (fully black, top left corner partly chipped off) !
Yet, the phone is not completly dead:
- The alarm keeps ringing at each time I have scheduled (several each morning )
- I'm able to switch off the alarm by by swiping left through the bottom of the screen, or by pressing the on/off button
- when I plug phone to my PC (win10) I can hear the bip-bip typical of a device connection, but nothing else happens
- On a PC on which the phone had never been connected, Windows recognised the phone and installed the drivers, but again Windows doesn't ask me what to do with the phone
- bluetooth seems to be working as the phone is seen as available by other devices
I'm trying to find a solution to access some of the data in my phone. Primarily the DCIM folder.
I would like to reboot in fastboot mode, as I believe I may have USB debugging on.
However I don't seem to be able to switch off the phone or reboot it.
Any idea how I could switch off the phone? Enter fastboot.
Do you think I could access the phone screen using an OTG device plugged to my computer screen via HDMI. If yes, which OTG device should I purchase?
Any other idea?
As a last resort, do you think it is possible to fully ripp-off the phone, get the flash drive and mount it somewhere in a tool that could be pluggin via USB?
Click to expand...
Click to collapse
Look for force reboot butto combination for your phone usually vol up/down + power button
The mounting option works but its quite advanced and you mmay need schematics or guess work lmao
You really don't want fastboot, you want ADB. Did you have ADB enabled before?
When it's connected to your Windows machines what is it showing? MTP (in File Explorer) or ADB?
Don't wait for Windows to ask questions!
Thank you for your help
When I connect my phone to the PC, there is just the connecting sound ("bip bip"), no ADB, no MTP
Since the phone screen is stuck to black, I don't know what's going on on the phone.
When first using the phone one year ago, I had activated ADB and used it to debloat the phone. I never removed ADB myself on the phone, but maybe it was deactivated (i don't know) after a system update. I would love to be able to check whether adb is still activated
When I type > adb devices in power shell with my OP plugged in, there is no device found.
So I believe this ADB option is off for me
Somehow USB debbugging must have been deactived
Also
Force-reboot doesn't seem to work
It may be that you don't have a Windows driver loaded.
Get UsbView.exe
The left pane should change as you disconnect/reconnect the USB cable.
Find the device that appears and disappears, select it, copy the contents of the right pane and post it here.
Renate said:
It may be that you don't have a Windows driver loaded.
Get UsbView.exe
The left pane should change as you disconnect/reconnect the USB cable.
Find the device that appears and disappears, select it, copy the contents of the right pane and post it here.
Click to expand...
Click to collapse
Thanks
Here is the screenshot (sorry my Windows OS is in French).
The new item when I plug my phone is :
[Loc23] DeviceConnected : Composite USB Device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ça ne me dit rien. (It doesn't tell me anything.)
I need the information on the right side when you click on Loc23.
Renate said:
Ça ne me dit rien. (It doesn't tell me anything.)
I need the information on the right side when you click on Loc23.
Click to expand...
Click to collapse
Ha so sorry, still mixing up right and left
OMG, your device is showing as a MIDI interface.
Er, that's not good.
Did you root your device with Magisk? Do you have anything useful on your desktop, boot.img or the Magisk'ed version?
Did you have TWRP recovery or some other?
Renate said:
OMG, your device is showing as a MIDI interface.
Er, that's not good.
Did you root your device with Magisk? Do you have anything useful on your desktop, boot.img or the Magisk'ed version?
Did you have TWRP recovery or some other?
Click to expand...
Click to collapse
No, I've never rooted this device. Never even attempted (with this one), so no Magisk, etc. The only "tweak" I did with it was removing some bloatwares using adb (I did this one year ago, right after purchasing it).
A MIDI interface.... I don't know.... But an alarm clock, for sure
If we're talking about the OnePlus Nord 2, that's a MediaTek.
You could go to a cell phone repair place and let them put in a new screen.
You could buy a screen. You don't need to actually install it. You can just connect it to the old cable and leave it flopping.
I don't think that your device has video out (USB Type C alt mode of DP or HDMI or MHL)
You could pull a copy of your boot image using MTK Client.
You could get someone to give you a boot image or a Magisk'ed image.
A small tweak to the boot image would have it come up as ADB or MTP.
Renate said:
If we're talking about the OnePlus Nord 2, that's a MediaTek.
You could go to a cell phone repair place and let them put in a new screen.
You could buy a screen. You don't need to actually install it. You can just connect it to the old cable and leave it flopping.
I don't think that your device has video out (USB Type C alt mode of DP or HDMI or MHL)
You could pull a copy of your boot image using MTK Client.
You could get someone to give you a boot image or a Magisk'ed image.
A small tweak to the boot image would have it come up as ADB or MTP.
Click to expand...
Click to collapse
Thank you so much for your help.
Changing the screen is not an option, given my phone's current state of destruction... it looks like a miracle the alarm clock still works, and the phone is still responsive to wiping the screen to turn it off
I will have a look at MTK Client, but it may be beyond my skill. Would you have a link to a good tutorial? Also, what would be the "small" tweak needed to the boot image?
They call that format of a phone "candy bar", but that doesn't mean that you should nibble on the corner!
This is the open source (Python) MTK client: https://github.com/bkerler/mtkclient
Hey! Any of you OnePlus Nord2 owners have a boot image to share? A Magisk'ed boot image would be even better.